Emit more information for summarizer observability

[kian-thompson]

By providing a way to programmatically observing summarization failures we can make progress in mitigating/reducing summarizer related issues. Customer OCE's will be able to catch a summarization bugs on their own and decide what to do with their end-users (either alert them via UI, alert themselves via Telemetry, etc.). Customers can also do their own summarization testing, and thus catch some of these bugs before they ship.

Included in this change are new events being emitted off the ContainerRuntime class and IContainerRuntime interface. They include:

• "summarizeAllAttemptsFailed": All attempts to summarize have failed.
• "lastSummaryAttempt": After stopping the summarizer, we run one final summarize attempt. This event is that result
• "summarizerStop": The summarizer has stopped, providing information on why and potential error.
• "summarizerStart": The summarizer has started.
• "summarizerStartupFailed": The summarizer has failed to startup, usually meaning it wasn't able to catchup. Includes information on why startup failed.

AB#24393

[github-actions[bot]]

🔗 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:
  170006 links
    1595 destination URLs
    1825 URLs ignored
       0 warnings
       0 errors