feat(iframe): implement wallet_getCapabilities method

[ultraviolet10]

Linked Issues

Description

Implements the spec for wallet_getCapabilities for the wallet to be able to specify the same to developers.

spec | porto docs for the same

🎲 demo(react): the demo's namesake button prompts the user to check the console for the expected payload.

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.

< INDICATE BROWSER, DEMO APP & OTHER ENV DETAILS USED FOR TESTING HERE >

< INDICATE TESTED SCENARIOS (USER INTERFACE INTERACTION, CODE FLOWS) HERE >

• 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 & 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) for changes that touch npm published packages (currently pacakges/core and packages/react), see here for more info.

[ultraviolet10]

• feat: implement wallet_getCallsStatus request handler #527
• feat: implement wallet_sendCalls request handler #526
• feat(iframe): implement wallet_getCapabilities method #525 👈 (View in Graphite)
• monorepo-wide viem update #524
• master

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

[ultraviolet10]

only capability we currently support!

[cloudflare-workers-and-pages]

Deploying happychain with    Cloudflare Pages

Latest commit:	be88f94
Status:	✅  Deploy successful!
Preview URL:	https://b7e710ff.happychain.pages.dev
Branch Preview URL:	https://aritra-5792-get-capabilities.happychain.pages.dev

View logs

[not-reed]

i guess should also check if the length is one, and if any of the chains are happyChain/currentChain (if they only request mainnet right now, it would not behave correctly)

[not-reed]

you could compute this once at a global level, instead on each request

// support/wallet-common/lib/interfaces/eip5792.ts
export const walletCapabilities = Object.fromEntries(
    Object.values(HappyWalletCapability)
        .map((capability) => [capability, { supported: true }])
)

Suggested change

	[currentChainId]: Object.fromEntries(
	Object.values(HappyWalletCapability).map((capability) => [capability, { supported: true }]),
	),
	[currentChainId]: walletCapabilities,