Add Embed Faucet route and update related components

[ultraviolet10]

Linked Issues

closes https://linear.app/happychain/issue/HAPPY-509/faucet-available-via-top-button-instead-of-a-popup

Description

This PR moves the faucet functionality from a tab in the wallet interface to its own dedicated route at /embed/faucet. The change improves the user experience by making the faucet accessible via a "Top Up" action button in the main interface.

Key changes:

• Created a new route /embed/faucet that hosts the faucet functionality
• Removed the faucet tab from the wallet content tabs
• Added a "Top Up" action button that links to the new faucet route
• Improved the faucet UI with better status messaging and styling
• Fixed a typo in the UseTurnstileArgs type name
• Updated the SwapIcon import to use the correct naming convention

Toggle Checklist

Checklist

Basics

• B1. I have applied the proper label & proper branch name (e.g. norswap/build-system-caching).
• B2. This PR is not so big that it should be split & addresses only one concern.
• B3. The PR targets the lowest branch it can (ideally master).

Reminder: PR review guidelines

Correctness

• C1. Builds and passes tests.

• C2. The code is properly parameterized & compatible with different environments (e.g. local,
  testnet, mainnet, standalone wallet, ...).

• C3. I have manually tested my changes & connected features.

• C4. I have performed a thorough self-review of my code after submitting the PR,
  and have updated the code & comments accordingly.

Architecture & Documentation

• D1. I made it easy to reason locally about the code, by (1) using proper abstraction boundaries,
  (2) commenting these boundaries correctly, (3) adding inline comments for context when needed.
• D2. All public-facing APIs are documented in the docs.
  Public APIS and meaningful (non-local) internal APIs are properly documented in code comments.
• D3. If appropriate, the general architecture of the code is documented in a code comment or
  in a Markdown document.
• D4. An appropriate Changeset has been generated (and committed) with make changeset for
  breaking and meaningful changes in packages (not required for cleanups & refactors).

[ultraviolet10]

• Add Embed Faucet route and update related components #891 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[linear]

HAPPY-509 Faucet available via top button instead of a popup

#661 (comment)

[cloudflare-workers-and-pages]

Deploying happychain with    Cloudflare Pages

Latest commit:	ed4033c
Status:	✅  Deploy successful!
Preview URL:	https://a54e673e.happychain.pages.dev
Branch Preview URL:	https://aritra-faucet-page.happychain.pages.dev

View logs

[norswap]

is there a faucet icon 👀

[norswap]

Text should say "Faucet" too

[not-reed]

topup should stay I think (and stay disabled) faucet is separate and exclusive feature to testnet

[norswap]

• There's a lil graphical glitch when the cloufdlare thing goes up, a horizontal scrollbar appears at the bottom.
• I like the spinner on the button, but it'd be better if it retained its original size.

But besides that, I'm of two minds on this. It look kinda better as a tab (feels very empty otherwise). Also, it's kinda cool if we can get the balance show up top to refresh when the faucet hits. Let's discuss.

[not-reed]

it's kinda cool if we can get the balance show up top to refresh when the faucet hits

I think it does this on master now (so assuming it works here, but i'm rate limited now 😓 )

I think i like it as a tab better

but with that said, our tabs could be good to be routes: https://ark-ui.com/docs/components/tabs#router-controlled-tabs

[norswap]

Aight, let's keep as a tab for now!