DOCS: New Timing and Latency section (DOCF-1179)

[duckets]

Description

Adds a section to the docs dedicated to timing and latency.
https://jira.unity3d.com/browse/DOCF-1179

Changes made

Pages added, TOC updated.

Testing

Built and checked locally.

Risk

Docs only change. No technical risk.

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.

[jo-unity]

Left some comments. Have you run this markdown through Vale? I think there's probably some minor stuff it would highlight which you might want to fix.

I think in terms of structure it might need tweaking, especially on the pages that have task and conceptual info on.

Also, I'm not sure if it would make sense to use the suggested file naming convention here for these files? https://docs.unity.com/internal/content-ops/en-us/documentation/content-dev/hexadocs/file-naming-conventions (i know it says it's for hexadocs but it's probably relevant everywhere)

[jo-unity]

I spotted a few formatting things. But overall I think the layout and everything works well.

The only other thing that I can think of that's missing from the New way of doing things is that all pages need "Additional resources" links at the end.

Am approving anyway as all this stuff shouldn't be a blocker to landing this.

[lyndon-unity]

Looks good. Looking forward to having this live on the documentation page