chore: upgrade unified bridge SDK

[meeh0w]

Description

• CP-9112
• CP-8047

TODOs

• Release @avalabs/bridge-unified to a stable channel

Changes

• Upgrades @avalabs/bridge-unified dependency
  • The new version includes some breaking changes. This PR updates our code to make it compatible.
• Refactors how we "recognise" CCTP (and the upcoming ICTT) bridge transactions - previously we would look at UnifiedBridge config to fetch the addresses, with this PR the updated SDK exposes the analyzeTx() method that we can use.
• Implements a schema migration for any pending bridge transfers (the BridgeTransfer object changed its shape, some properties changed names and/or places)

Testing

• Test bridging. It should work exactly the same as it used to.
• Run sanity checks on other parts of the extension
• Bonus points for simulating the extension update (initiate bridging from main, switch to this branch and verify that your transaction is still tracked properly).

Screenshots:

Starts bridging via CCTP on main, simulates the extension update, then starts another bridge with the "updated" extension:

CCTP.after.update.-.compressed.mov

Checklist for the author

• I've covered new/modified business logic with Jest test cases.
• I've tested the changes myself before sending it to code review and QA.

[gergelylovas]

should we add tests for these?

[meeh0w]

The getAssetIdentifierOnTargetChain will be removed as soon as ICTT is finalized, so I wouldn't bother personally.

isBridgeTx is now analyzeTx - I'll add tests in the upcoming PR (here: #57)