fix: fox discount ux

[0xApotheosis]

Description

On the fox route:

• Ensures the FOX power value updates as the value in the store updates
• Prevents the FOX power value from refreshing if the FeeSliders have already been interacted with (i.e. once you interact with it you're in override mode)
• Adds a loading skeleton on the amount input when the selectIsSnapshotApiQueriesPending selector returns true
• Improves the naming inside the component

Issue (if applicable)

Closes https://github.com/shapeshift/web/issues/8123

Risk

Small (UI changes only)

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

None

Testing

• Whilst connect to a wallet with some FOX, load the /fox route with a fresh cache. The FOX Power value should have a loading skeleton whilst it is doing so. Once a value is fetched the value should be shown (instead of the previous, bug of showing 0).

Engineering

☝️

Operations

• [ ] :checkered_flag: My feature is behind a flag and doesn't require operations testing (yet)

☝️

Screenshots (if applicable)

See testing step.

[0xApotheosis]

@NeOMakinG does the 480 FOX come from another EVM at the same address, or from a different previously connected wallet?

Assume it's the former, and agree it could be confusing - that said, if a user has FOX on another chain they are probably a power-ish user and would likely understand this to some degree.

[NeOMakinG]

@NeOMakinG does the 480 FOX come from another EVM at the same address, or from a different previously connected wallet?

Assume it's the former, and agree it could be confusing - that said, if a user has FOX on another chain they are probably a power-ish user and would likely understand this to some degree.

I think same address but unsupported chain from our interface with the selected wallet (ex: Arbitrum but using Phantom)

Seems like the snapshot API returns the voting power for every chains and strategies it supports regardless if our interface is currently supporting it