Util for testing permission changes

[aklinker1]

Feature Request

When updating permissions or adding content scripts, it's useful to know if the browser will disable your extension and prompt the user to accept the new permissions.

I'd like to add a wxt check-permissions command that generates two CRX files, one for the previous tag, and one for the current head, then walks you through installing both to see if your change will disable the app on update.

Full command might look like this:

wxt check-permissions --against <ref>

1. Make sure we know the path to chrome
2. Do a wxt zip against the current head
3. If there changes have not been committed, prompt to stash them or exit if not
4. Checkout the last tag or the --against ref
5. Run a zip again, downgrading the version to 0.0.0-<ref>
6. Create a CRX without a private key based of the older commit's zip
7. Create a CRX with the private key output by the last step on the current head's zip
8. Print instructions to install and test manually

Is your feature request related to a bug?

N/A

What are the alternatives?

I am not aware of any tools for testing permission updates like this.

Additional context

N/A