docs: update Presence throttling notes

[jason-ha]

to match presence package readme.

Throttling implementation was added in v2.11.0.

[Josmithr]

Not for this PR, but this reminded me: I'm trying to establish a pattern for maintaining "living" code examples for use in docs contexts like this. I'd be interested in your thoughts on it.

PR: #23324

[jason-ha]

I like living examples. To be most effective they would have to be tied to the released code. But most docs are slightly divorced from what is released. That means updating after or with release and we'll mess it up. I support figuring it all out for sure.

[Josmithr]

But most docs are slightly divorced from what is released.

True in a lot of cases, but for package-local documentation like this, the two should generally be in-sync.

[jason-ha]

Main docs are from main branch and API docs are from latest released branch. That 2-to-3-week possible disparity is what you mean by "generally in-sync"?

[github-actions]

🔗 No broken links found! ✅

Your attention to detail is admirable.

linkcheck output

> fluid-framework-docs-site@0.0.0 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"


> fluid-framework-docs-site@0.0.0 serve
> docusaurus serve --no-open

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

> fluid-framework-docs-site@0.0.0 check-links
> linkcheck http://localhost:3000 --skip-file skipped-urls.txt

Crawling...

Stats:
  170142 links
    1596 destination URLs
    1825 URLs ignored
       0 warnings
       0 errors