Publish v6.3.0 extension + web app

[grod220]

• Manual testing to confirm extension works with main flows
  • Balances
  • Send
  • Swap
  • Staking
  • IBC (not ready)
  • Tx details
  • Test sync with assertRootValid() enabled. Will throw if TCT roots are not correct. Only test the first few dozen blocks; if those succeed, there's no need to keep going.
• If there is already a changelist PR (like this one), merge it. Otherwise, manually run pnpm changeset to bump packages as needed (would require work looking through PRs since last version) and run pnpm changeset version after. If this has resulted in a change to the package.json version in the extension, update the extension's manifest.json version to match. You'll have local changes that will require a PR to merge.
  • This step will publish updated npm packages.
• Update manifest version based on the extension's newly updated package.json version in the extension.
• Create repo release with vX.X.X tag. Triggers approval to run chrome extension publishing.
• In the repo root, run sh ./scripts/build-for-deployment.sh. It will create two .zip files. Use those files to open a PR against core repo to update the node's frontends. Skipping this release
• Wait 1-3 days until new extension version is live on chrome web store
• Run Deploy Static Site github action
• Work with comms team for relevant discord announcements and social posts for new features we want to amplify