Re-enable Noble withdraws

[grod220]

Following the v0.80.0 core release, clients now have the ability to use the new useCompatAddress flag that fixes issues with Ics20Withdraws to chains that use the bech32 address standard (versus bech32m).

Updates required to enable Noble

penumbra-zone/web pt. 1 updates - #1623 (merged ✅ )

• bump penumbra crate deps to v0.80.0
• bump decaf377 v0.10.1 (@TalDerei fyi)
• bump bufbuild types in penumbra-zone/web
• Update action views to include useCompact flag (tx details page)
• Note: do not remove the Noble blocker yet in the UI
• Userflows to test (with current extension version):
  • Current IBC userflows (eg. UM -> Osmosis, OSMO -> osmosis)
• publish new versions to npm Version Packages #1650

prax-wallet/web updates - prax-wallet/prax#144 (merged ✅ )

• Updates to latest penumbra-zone/packages (from above)
• Update action views to include useCompact flag (approval dialog)
• Userflows to test on penumbra-1:
  • USDC deposit, USDC withdraw with no other assets in account (tests multi-asset fees)
  • USDC withdraw to noble using UM as gas
  • Send UM to noble. Note: This is sort of a strange userflow (along with UM->cosmos hub) as UM isn't listed in those respective registries, wallets don't recognize it, and there isn't really anything you can do with UM on those chains.
  • Misc other Ics20Withdraws to ensure no breakage with already working chains.
• Submit for Chrome Review (pending ⚠️)
• Wait 24 hours for approval before moving to last step

penumbra-zone/web updates pt. 2 - #1658

• In the UI, remove the block on Noble transfers
• Merge
• Wait to see latest commit on auto-deploy frontends. Will happen within 6 hours.
• Notify Radiant that UI fixes are coming soon

Comms

Radiant to issue discord message + tweets about re-enabled feature