Feature: Fetch Fastest RPC For Rewards dApp

[barebind]

Resolves #130

• Using integers instead of hexes for networkId/chainId is less confusing and also is compatible with specs.
• Fixed some missing parts/fields for scripts/typescript/generate-permit2-url.ts
• network parameter in the url is not used so I removed it. networkId fromClaimTx is used instead.
• More structured multi-chain network config might be a better use.
• onboarding has it's own switchNetwork functions etc. Some functions are shared across different UIs and some are not. Definitely confusing for newcomers.
• isNonceClaimed always returns true for a new setup(new ubiquibot account) on Goerli. Something must be missing in the documentation. Don't know what and why.
• For getOptimalRpc() functionality. The current approach is definitely not the best one as it always calls whenever it needs rpc provider. There must be some context to store optimal provider and fetching optimal RPC must be on page load or something.
• Optimal RPC as a concept cannot be applied to Metamask because if an already added network has a slow rpc provider on Metamask side, there is no edit option as far as I know. So using optimal RPC provider is for only backend calls like transaction data rendering, fetching nonces etc. but sending a transaction through Metamask is via it's own stored rpc provider for chainId.

[ubiquibot]

3d9e071