fix: notifications don't render correctly

[npty]

Description

This PR fixes a lot of issues related to notifications don't render correctly after the token deployment. The bonus changes are supporting devnet-amplifier to various packages in the sdk.

Changes

• Fix the loading status never change in notification
• Fix the notification doesn't support multiple destination chains due to we pass deploymentMessageId as the tx hash.
• Fix the invalid axelarscan link in notification (tx_hash:log_index -> tx_hash-log_index)
• Fix the notification is not dismiss-able.
• Enhanced transaction tracking to correctly handle two-hop transactions by showing status details for both Axelar (intermediary chain) and the final destination chain.
• Support devnet-amplifier in multiple axelarjs packages (see changeset file).

Screenshots

[changeset-bot]

🦋 Changeset detected

Latest commit: 5033cd3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 7 packages

Name	Type
@axelarjs/transaction-recovery	Patch
@axelarjs/cosmos	Patch
@axelarjs/core	Patch
@axelarjs/api	Patch
@axelarjs/evm	Patch
@axelarjs/maestro	Patch
@axelarjs/deposit-address	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
axelar-maestro	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 13, 2025 10:50am
axelar-registry	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 13, 2025 10:50am
axelar-ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 13, 2025 10:50am
axelarjs-maestro-devnet-amplifier	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 13, 2025 10:50am