feat: don't fetch NFTs meta from routes other than dashboard

[gomesalexandre]

Description

Does what it says on the box - we were previously fetching NFTs data in <AppContext /> regardless of route, which was effective overfetching

Issue (if applicable)

• contributes to actually closes NFT related spew on initial load #8167 - doesn't rate-limit things, but by ensuring we fetch at the right place, and not in swapper which doesn't need this data, we effectively make things much better already, and retries are already implemented by virtue of us consuming the Alchemy SDK. See NFT related spew on initial load #8167 (comment) for context

Risk

High Risk PRs Require 2 approvals

Low to none

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

Testing

• Filter network requests for alchemy while in initial app trade route
• Ensure no alchemy XHRs are made
• Go to wallet route and notice how alchemy NFT data is fetched

Engineering

• In addition to the testing above, you may want to paranoia add a breakpoint in useNFTs() and confirm it doesn't get hit on initial trade route, but only lazily when navigating to wallet route

Operations

• 🏁 My feature is behind a flag and doesn't require operations testing (yet)

• ^

Screenshots (if applicable)

https://jam.dev/c/175dae9c-cfc6-40c0-a691-90a7603ffefa