feat: Add timing code to Tasks code block rendering code

[claremacrae]

Description

• Add new user debug setting recordTimings, which optionally enables new console output from new class PerformanceTracker.
• Look at the diffs in this PR to see:
  • the docs of PerformanceTracker
  • and the new Console timing facilities in Tasks.md
• Tasks-Demo vault:
  • Add range of query files (limit 1.md .... limit 5000.md) to the 'Stress Test' folder, to quickly get search and rendering timings
• Contributing vault:
  • Add new page to Contributing docs: 'Console timing facilities in Tasks'

Motivation and Context

• To make it easier to get elapsed times for critical sections of code
• To make it easier to interpret performance flame charts.

How has this been tested?

• Using it to time the rendering of search results
• Viewing flame charts

Screenshots (if appropriate)

To create these outputs, the setting debugSettings > recordTimings was set to true.

Example console output:

Search: 4tNIzakiWp - Stress Test/limit 1.md: 131.60000002384186 milliseconds
Render: 4tNIzakiWp - Stress Test/limit 1.md: 26.900000035762787 milliseconds
Search: 63ata8hRM1 - Stress Test/limit 25.md: 89.20000004768372 milliseconds
Render: 63ata8hRM1 - Stress Test/limit 25.md: 32.30000001192093 milliseconds
Search: XxLS3Z3SHT - Stress Test/limit 50.md: 101.10000002384186 milliseconds
Render: XxLS3Z3SHT - Stress Test/limit 50.md: 62.80000001192093 milliseconds
Search: 7T4xmf87Ky - Stress Test/limit 100.md: 108.5 milliseconds
Render: 7T4xmf87Ky - Stress Test/limit 100.md: 165.79999995231628 milliseconds
Search: XngShdTbz3 - Stress Test/limit 150.md: 91.40000003576279 milliseconds
Render: XngShdTbz3 - Stress Test/limit 150.md: 164 milliseconds
Search: aCvrb1aufJ - Stress Test/limit 200.md: 91.10000002384186 milliseconds
Render: aCvrb1aufJ - Stress Test/limit 200.md: 209.89999997615814 milliseconds

Example screenshot of labels in profiling timings

Types of changes

Changes visible to users:

• New feature (prefix: feat - non-breaking change which adds functionality)
• Sample vault (prefix: vault - improvements to the Tasks-Demo sample vault)
• Contributing Guidelines (prefix: contrib - any improvements to documentation content for contributors - see Contributing to Tasks)

Checklist

• My code follows the code style of this project and passes yarn run lint.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• My change has adequate Unit Test coverage.

Terms

• My contribution follow this project's contributing guide
• I agree to follow this project's Code of Conduct