Include better error handling and messaging for unrecoverable idb error

[fungairino]

Describe the feature

Users will sometimes encounter a "Internal error opening backing store for indexedDB.open" error in various places. We have added retry handling and recovery mechanisms to try to get IDB back to a good state, but in certain cases this error simply isn't fixable by the extension and requires the user to perform some manual debugging steps.

Example user still experiencing this issue: https://app.datadoghq.com/logs?query=issue.id%3Aea6ca0fc-0b23-11ef-ad2c-da7ad0900002%20%40extensionVersion%3A2.1.4%20&agg_m=count&agg_m_source=base&agg_q=%40usr.email&agg_q_source=base&agg_t=count&cols=host%2Cservice&fromUser=true&messageDisplay=inline&refresh_mode=sliding&storage=hot&stream_sort=desc&top_n=10&top_o=top&viz=timeseries&x_missing=true&from_ts=1728413687395&to_ts=1728500087395&live=false

Acceptance criteria

• Add a try-catch and specific error reporting to note that this unrecoverable error occurred when we attempted to delete the indexDB databse
  • https://github.com/pixiebrix/pixiebrix-extension/blob/7952c3d61da343b285819417003db0442a8e571b/src/utils/idbUtils.ts#L257
• Display error message to user.
  • We can link them to this specific troubleshooting steps in a banner notification error message that we show on the extension console or page they are currently on: https://docs.pixiebrix.com/how-to/troubleshooting/troubleshooting-indexeddb-errors

Context

https://pixiebrix.slack.com/archives/C07MJ3LJ66B/p1728500238173139 https://github.com/pixiebrix/pixiebrix-extension/pull/9252

[twschiller]

@Pashaminkovsky for additional context - if PixieBrix can't connect to the DB on extension page load it shows a banner in the Extension Console/Sidebar/Page Editor with a link to our troubleshooting docs: https://docs.pixiebrix.com/how-to/troubleshooting

This feature might additionally show:

1. A banner on the page if a mod errors due to an IDB issue
2. A more informative error message in the panel

[Pashaminkovsky]

Let's revisit the priority here if excluding IndexedDB from syncing doesn't resolve the issue