feat: base HyperLiquid activation detection on spot sends and creation fees

[dan437]

Explanation

The hyperliquidActivationFee reserve added in #9238 decides whether to hold back the one-time HyperLiquid activation fee by probing userNonFundingLedgerUpdates. It currently treats any outbound ledger entry as proof of activation, including bridge withdraw entries, and assumes the account is activated whenever the probe fails.

That does not match how HyperLiquid charges the fee. Verified against the live API:

• The fee is charged once per HyperCore account.
• If an inbound spot transfer creates the account, the fee is charged on that transfer and recorded on the account's first ledger entry (fee: "1.0"). All later sends are then fee-free.
• Accounts created another way (bridge deposit, perps trading) pay the fee on top of their first outbound spot send.
• Bridge withdrawals use a separate fee lane and do not settle spot activation.
• When an account's balance reaches zero it is purged together with its ledger, which also resets activation.

So an account whose only outbound history is bridge withdrawals is still unactivated for spot sends. The probe classified such accounts as activated, skipped the reserve, and their max withdrawals failed on the sendAsset step with Insufficient USDC balance for token transfer gas.

This PR reworks the detection:

• Bridge withdrawals no longer count as activation.
• An account counts as activated when its earliest ledger entry carries a fee of at least 1 (activation paid at creation), or when it has a prior outbound send/spotTransfer. A fee on a later inbound entry is ignored, because it belongs to the sender's own first-send activation.
• Probe failures now reserve the fee instead of skipping it. Wrongly reserving leaves a small, recoverable balance on HyperLiquid; wrongly skipping fails the entire withdrawal.

It also fixes the feature flag lookup that gates the reserve. Most withdrawals are wrapped in an EIP-7702 batch, so the parent transaction type is batch and the overrides.perpsWithdraw.hyperliquidActivationFee config was never matched — the reserve was silently disabled for those accounts before the activation probe even ran. The override is now resolved through the first typed nested transaction when the parent is a batch, matching the existing type resolution in the relay submit and fiat strategies. In the meantime we solved this already in prod via a LD change.

Max withdrawals then leave no leftovers: activated accounts send 100% of their balance, and unactivated accounts reserve exactly the fee, which HyperLiquid consumes, so the account ends at zero.

References

• Follow-up to feat: reserve HyperLiquid activation fee for unactivated Pay withdrawals #9238
• Related to CONF-1689

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them