FIX: Add missing manuals for the tracked input devices components (ISXB-1410)

[K-Tone]

Description

This pull request adds two new sections that were priorly missing and causing broken link reports.

Testing status & QA

This is purely a docs change really, nothing's really going to be broken all that much.

Overall Product Risks

• Complexity: Low
• Halo Effect: Low

Comments to reviewers

None.

Checklist

Before review:

• Changelog entry added.
  • Explains the change in Changed, Fixed, Added sections.
  • For API change contains an example snippet and/or migration example.
  • JIRA ticket linked, example (case %%). If it is a private issue, just add the case ID without a link.
  • Jira port for the next release set as "Resolved".
• Tests added/changed, if applicable.
  • Functional tests Area_CanDoX, Area_CanDoX_EvenIfYIsTheCase, Area_WhenIDoX_AndYHappens_ThisIsTheResult.
  • Performance tests.
  • Integration tests.
• Docs for new/changed API's.
  • Xmldoc cross references are set correctly.
  • Added explanation how the API works.
  • Usage code examples added.
  • The manual is updated, if needed.

During merge:

• Commit message for squash-merge is prefixed with one of the list:
  • NEW: ___.
  • FIX: ___.
  • DOCS: ___.
  • CHANGE: ___.
  • RELEASE: 1.1.0-preview.3.

After merge:

• Create forward/backward port if needed. If you are blocked from creating a forward port now please add a task to ISX-1444.

[unity-cla-assistant]

All committers have signed the CLA.

[ekcoh]

Thanks for adding this documentation. I think it looks good and I believe it is good that it links further into the script Api documentation that already existed. Also great you added CHANGELOG entry. It makes sense that some feedback is received from XR side as well before landing this.

[Pauliusd01]

Sounds a bit "fluffy/marketingy" at times but overall fine to me

[JonMUnity]

Made some minor suggestions. Let me know if you have any questions!

[vrdave-unity]

Looks good from my side. You might consider using xref: in the future for the API references from the manual, just in case any of the namespaces or structure moves around your doc references don't break.