Cardano Updates

* fix: Expose active account stream while respecting keychain status

* fix: Revert some changes

* cleanup

* refactor

* refactor

---------

Co-authored-by: Damian Moliński <[email protected]>

- Added support for dark and light themes in the EarnRewardsBanner component.
- Updated the gradient colors to reflect the current theme, enhancing visual consistency.

- Add Airdrop menu item and screen for NIGHT token redemption
- Implement redemption API integration with thaw schedule checking
- Add eligibility check and banner notification in transaction history
- Support gradual token unlocking (thawing) with four 25% installments
- Add address allocation display with thaw schedule and redemption status
- Implement transaction building and signing for token redemption
- Add proper error handling for readonly wallets and uninitialized wallets
- Use existing usePromptRootKey hook for secure password entry
- Format addresses using ellipsizeMode middle with highlighted suffix
- Use intl.formatDate for consistent date formatting
- Apply theme atoms and spacing for dark mode compatibility
- Only show airdrop feature on mainnet wallets

Only allow `PlutusV1` when parsing cost models in `AlonzoGenesis`
and `UpgradeAlonzoPParams`.

* Override cost models when injecting into test state (if extra config
cost models are provided)
* Preserve `AlonzoGenesis` JSON and binary representations but change
the Haskell side representation

* fix: Fix installation of new versions of firefox-esr

Signed-off-by: Evgeniy Dikevich <[email protected]>

* Add catalyst-qa into notification list

Signed-off-by: Evgeniy Dikevich <[email protected]>

---------

Signed-off-by: Evgeniy Dikevich <[email protected]>

Signed-off-by: etorreborre <[email protected]>

Implement interval-based rate limiting (~100 blocks/sec) in the subscription
loop to prevent memory exhaustion and OOM kills during blockchain indexing.

Problem:
Network produces blocks at high throughput (100s/sec) while WASM processes
significantly slower. Resources are created in DashMap BEFORE bounded event
queue send() can apply backpressure. Even with a 10K bounded channel, resources
accumulate in memory while waiting for queue space, leading to unbounded growth
and OOM kills (exit code 137) within minutes.

Solution:
Rate limit block processing using tokio::time::interval at the TOP of the
subscription loop, before pulling blocks from the network. This matches resource
creation rate to WASM consumption rate (~100 blocks/sec), preventing accumulation.

Changes:
- Add BLOCK_RATE_LIMIT_MS constant (10ms interval)
- Replace tokio::select! on follower.next() with interval-based tick
- Set MissedTickBehavior::Skip to prevent tick accumulation
- Add detailed comments explaining resource lifecycle and ordering problem
- Add TODO for future lazy resource creation approach

Works in conjunction with bounded event queue (10K capacity) - both mechanisms
are required because resources exist before backpressure can apply.

Note: Rate limiting is a pragmatic fix for the current event-driven architecture.
Long-term solution should use lazy resource creation (send Arc<BlockData> in
events, create resources on-demand when WASM accesses them) to eliminate the
ordering problem entirely

* wip: initial tab & route setup

* wip: home header & profile

* wip: tiles

* wip: tiles colors

* wip: tiles translation and scan modal

* wip: tile coming soon badge

* wip: dapp - connections - rotate

* fix: rotate - split section - new tests

* fix: group selector for split section

* fix: remove responsive grid from small screens