feat(chrome-devtool): migrate to Manifest V3 with Plasmo framework

[OpenGG]

Before submitting a pull request, please make sure the following is done...

• Ensure the pull request title and commit message follow the Commit Specific in English.
• Fork the repo and create your branch from master or formily_next.
• If you've added code that should be tested, add tests!
• If you've changed APIs, update the documentation.
• Ensure the test suite passes (npm test).
• Make sure your code lints (npm run lint) - we've done our best to make sure these rules match our internal linting guidelines.

Please do not delete the above content

---

What have you changed?

feat(chrome-devtool): migrate to Manifest V3 with Plasmo framework

• Refactor architecture to comply with Manifest V3 security requirements
• Preserve devtools functionality with updated service worker lifecycle
• Fix requestIdleCallback() bug in backend.ts
• Replace legacy toolkit with Plasmo framework for enhanced DX
• Implement automatic HMR for popup/options UI components
• Update build chain and dependency tree (React 18.3.1)
• Add release devtools workflow configuration

BREAKING CHANGE: Requires Chrome 88+ due to Manifest V3 changes

[CLAassistant]

All committers have signed the CLA.

[Galileo01]

awsome

[wweggplant]

@janryWang 大佬麻烦看下这个浏览器扩展更新得pr

[liuweiGL]

试用了一下，这个插件同步表单数据时有点问题，插件展示的跟真实的表单状态不一致

[OpenGG]

@liuweiGL Thank you for flagging this potential inconsistency issue. I’d like to investigate further. Could you please share the steps to reproduce it?

[OpenGG]

试用了一下，这个插件同步表单数据时有点问题，插件展示的跟真实的表单状态不一致

​​Issue:​​ Reproducible inconsistency in messaging during extension idle state.

​​Possible Cause:​​ Service worker (SW) inconsistency—when the extension idles and the SW terminates, the content script fails to bridge messages to the extension, triggering the error:
Uncaught (in promise) Error: A listener indicated an asynchronous response... message channel closed before a response was received.

​​Proposed Solution:​​ Refactor messaging logic to handle inconsistent SW states, such as implementing a wake-up protocol for the service worker before critical operations and improving error resilience in message handling.