Fix incorrect method names and incomplete trigger description in InteractionTracker state table

[Copilot]

The InteractionTracker state transition table contained two categories of errors: incorrect method names (TryUpdatePositionWithVelocity/TryUpdateScaleWithVelocity — these methods don't exist) and an overly restrictive "only happens when" claim for the Idle→Inertia transition that excluded mouse wheel input as a trigger.

Changes

• Idle → Inertia: Removed the incorrect "only happens" qualifier; added that input such as mouse wheel scroll can also trigger this transition. Corrected method names to TryUpdatePositionWithAdditionalVelocity / TryUpdateScaleWithAdditionalVelocity.
• Inertia → Inertia: Same method name corrections.
• CustomAnimation → Inertia: Same method name corrections.

Note: When the Idle→Inertia transition is triggered by mouse wheel (rather than a TryUpdate* call), the requestId in the state-entered args will be 0, consistent with how user-input-driven transitions are reported.

• Fixes Incorrect documentation for InteractionTracker #100

[Copilot]

Pull request overview

Updates the InteractionTracker documentation to correct method names in the state transition table and to accurately describe additional triggers for the Idle → Inertia transition (including mouse wheel input), aligning the docs with observed runtime behavior and WinAppSDK API surface.

Changes:

• Replaces non-existent TryUpdate*WithVelocity references with TryUpdate*WithAdditionalVelocity in relevant state transitions.
• Revises the Idle → Inertia trigger description to include user input (e.g., mouse wheel scroll) as a valid trigger, not only TryUpdate* calls.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.