Catch errors when getting from browser storage

[JamesNK]

Description

Getting values from session storage can fail if the user upgrades Aspire version, or starts and stops the standalone container, while leaving the browser open. The problem is that session state is preserved (the browser is still open) but the underlying encryption keys have changed. The data's now invalid.

Fix is to ignore errors when getting from session/local storage. In this case the session state is lost, but nothing important is saved there.

Fixes #6961

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

Microsoft Reviewers: Open in CodeFlow

[Copilot]

Copilot reviewed 5 out of 6 changed files in this pull request and generated no comments.

Files not reviewed (1)

• src/Aspire.Dashboard/Model/BrowserStorage/LocalBrowserStorage.cs: Evaluated as low risk

[eerhardt]

Does this need to be ILogger<T>? If it was just ILogger, then we wouldn't need to use the TSelf inheritance pattern and BrowserStorageBase could remain non-generic.