Prototype Evaluation: Unify passing low volume state change through single method across layers

[anthony-murphy]

Evaluating the idea of pushing all low volume state changes through a single method, rather than a method per state type.

The main advantage is we don't need to add a new method to all layers for every state new state or augmentation, the disadvantage is it is harder to do api based feature detection.

The loss of api based feature detection may however be mitigated by the fact that we now have a layer compat contract. in fact, it is hard to deal with both layer compat and api as they don't interoperate well, so pushes more types are changes into the layer compat contract may actually make it easier to manage.

The basic premise here is replace setConnectionState, setAttachState, noifyReadOnlyState, and setTombstone with a single method, notifyStateChange.

I didn't do it in this PR, but we could also consider bringing a change like this to the loader layer.

[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:
  163679 links
    1315 destination URLs
    1547 URLs ignored
       0 warnings
       0 errors