build(client-presence): type and lint fixes

[jason-ha]

Minor production runtime changes with introduction of getOrCreateRecord helper and retyping of Object.entries/keys utilities.

[github-actions]

🔗 No broken links found! ✅

Your attention to detail is admirable.

linkcheck output

> [email protected] ci:check-links /home/runner/work/FluidFramework/FluidFramework/docs
> start-server-and-test "npm run serve -- --no-open" 3000 check-links

1: starting server using command "npm run serve -- --no-open"
and when url "[ 'http://127.0.0.1:3000' ]" is responding with HTTP status code 200
running tests using command "npm run check-links"


> [email protected] serve
> docusaurus serve --no-open

[SUCCESS] Serving "build" directory at: http://localhost:3000/

> [email protected] check-links
> linkcheck http://localhost:3000 --skip-file skipped-urls.txt

Crawling...

Stats:
  170005 links
    1595 destination URLs
    1825 URLs ignored
       0 warnings
       0 errors

[msfluid-bot]

Code Coverage Summary

↓ packages.framework.presence.src:
Line Coverage Change: -1.21%    Branch Coverage Change: -0.63%

Metric Name	Baseline coverage	PR coverage	Coverage Diff
Branch Coverage	88.57%	87.94%	↓ -0.63%
Line Coverage	73.96%	72.75%	↓ -1.21%

---

Baseline commit: 5abfa01
Baseline build: 308954
Happy Coding!!

Code coverage comparison check failed!!
More Details: Readme

• Skip This Check!!

What to do if the code coverage check fails:

• Ideally, add more tests to increase the code coverage for the package(s) whose code-coverage regressed.

• If a regression is causing the build to fail and is due to removal of tests, removal of code with lots of tests or any other valid reason, there is a checkbox further up in this comment that determines if the code coverage check should fail the build or not. You can check the box and trigger the build again. The test coverage analysis will still be done, but it will not fail the build if a regression is detected.

• Unchecking the checkbox and triggering another build should go back to failing the build if a test-coverage regression is detected.

• You can check which lines are covered or not covered by your tests with these steps:

  • Go to the PR ADO build.
  • Click on the link to see its published artifacts. You will see an artifact named codeCoverageAnalysis, which you can expand to reach to a particular source file's coverage html which will show which lines are covered/not covered by your tests.
  • You can also run different kind of tests locally with :coverage tests commands to find out the coverage.