CI should validate build output and conduct function tests before uploading a CRX to the chrome store

[turbocrime]

Production builds generate different output than development builds. But output of the publish CI is neither verified nor available for inspection before it is published.

To Reproduce

1. Activate the Prax release workflow.
2. Good luck!

Expected behavior

The output of the release workflow should have some assurances.

Suggestions

Minimal:

1. confirm the output zip is not empty.
2. make the output zip available for download.
3. check the build for presence of development symbols.
4. ensure that chrome may install the build output.
5. ensure that chrome may successfully update from the immediate previous version.

High priority:

6. ensure onboarding is functional.
7. ensure that chrome may successfully update from a selection of previous versions.
8. confirm ability to connect to pd-bundled minifront and latest minifront.

Nice:

9. Run a suite of integration tests validating native transaction functionality.
10. Run a suite of integration tests validating ibc functionality.

Ideal:

11. Confirm behavior when connecting to outdated nodes.
12. Confirm behavior when connecting to outdated minifront.
13. Attempt connection to as many frontends as possible.

[grod220]

In the extension-upload.yml github action, we can hash the output with the dist attached to the release (will require us doing that). If it doesn't match, it can throw, preventing an upload.