feat: enhance MicroBridge functionality and improve transaction history styling

[EmekaManuel]

Bug: Fix Microbridge UI/UX Issues

#251

Description

This PR fixes two UI/UX bugs in the microbridge flow that were preventing users from creating multiple bridge transactions and causing visual inconsistency in the transaction history.

Issues Fixed

1. isBridging State Not Resetting: After creating a bridge request, users were unable to create another transaction because the isBridging state was never reset, blocking the UI even after the transaction completed successfully or failed.

2. fixed the font issue too with transaction amount

Impact: Users can now immediately create another bridge request after a transaction completes, without being blocked by the UI state.

Summary by Sourcery

Improve the MicroBridge flow to allow consecutive bridge transactions and enhance the readability of the transaction history UI.

Bug Fixes:

• Ensure the bridging state is reset once relay processing finishes so users can start a new bridge transaction after completion or failure.

Enhancements:

• Improve transaction history layout with truncation, overflow handling, and consistent typography for hashes, addresses, amounts, and fees to prevent wrapping and visual glitches.

[sourcery-ai]

Hey - I've left some high level feedback:

• The relayCompleted flag in MicroBridge is derived entirely from bridgeStatus/relayStatus, so consider computing it directly inside the effect instead of storing it in state to simplify the dependency array and avoid subtle state-sync bugs.
• The repeated targetChainId.toNumber() === 122 ? ... : ... checks for chain names and explorer chainId lookups in MicroBridgeController could be refactored into a small helper or mapping to reduce duplication and the risk of inconsistent updates.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The `relayCompleted` flag in `MicroBridge` is derived entirely from `bridgeStatus`/`relayStatus`, so consider computing it directly inside the effect instead of storing it in state to simplify the dependency array and avoid subtle state-sync bugs.
- The repeated `targetChainId.toNumber() === 122 ? ... : ...` checks for chain names and explorer `chainId` lookups in `MicroBridgeController` could be refactored into a small helper or mapping to reduce duplication and the risk of inconsistent updates.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[L03TJ3]

@EmekaManuel make sure in other PR's that related screens or demo-videos are included in the PR
not only on telegram.

Sharing here for visibility:

[L03TJ3]

I have no idea what all these changes are?
the only thing to fix was to have the font-sizing aligned.

It seems even (looking at the screenshot) that these proposed changes break previously working sections.
(it was a table based layout. your current UI does not align column-headers with the column)

(below is from our dev environment, not from your PR)