fix: Update Reload Manager Extension for Chromium to MV3

[Hibi-10000]

Related to #3388

Upgrade web-ext Reload Manager Extension to Manifest Version 3 to prevent it from being disabled by Chromium-based browsers.

[Rob--W]

Thanks for the PR. I am not merging this yet because there is other necessary work required to maintain long term support for Chromium browsers (#3388).

I had already noticed this issue before, but haven't migrated yet. It is not as trivial as bumping the manifest version + background property: In MV2, the background page is persistent, while in MV3 the background service worker may suspend on inactivity, which would break the WebSocket connection.

[Hibi-10000]

For your information, it seemed to work fine, at least when I tested it by running it for a short time.
(In fact, I confirmed that it is able to receive information via WebSocket.)
Of course, I suppose it would need to be tested with it running for a longer period of time.

[unmade-spangle]

Thanks for the PR. I am not merging this yet because there is other necessary work required to maintain long term support for Chromium browsers (#3388).

I had already noticed this issue before, but haven't migrated yet. It is not as trivial as bumping the manifest version + background property: In MV2, the background page is persistent, while in MV3 the background service worker may suspend on inactivity, which would break the WebSocket connection.

Thanks. I believe you can incorporate a self-ping to keep it alive, @plasmohq/persistent/background has this implemented.