follow up on today's frontend troubles

- currently convinced it was a rate limiting issue (or outage or similar) on cloudflare. would have been easy to check this in the browser's network tab, but i overlooked that at the time not thinking cloudflare was involved

- i've been making a wrong assumption about how wagmi works by default. by default it uses staticly configured public rpcs for all requests, read and write. we can configure our own rpcs. in fact wagmi actually recommends this for production here, https://wagmi.sh/core/api/transports/http#http

- i checked mom's web3 lib and see they customize wagmi with various rpcs. i dont see a github for it, but npm lets you read package code now if your interested, https://www.npmjs.com/package/@builtbymom/web3?activeTab=code
("web3" is mom's new "web-lib")

- for another example, i debugged the uniswap frontend and see it's using this paid infura url, https://mainnet.infura.io/v3/099fc58e0de9451d80b18d7c74caa7c1

- when I configure ycrv in dev to use a bad rpc url i see the same multicall behavior we saw intermittently earlier today.. ie repeating, total multicall fails, root cause not obvious unless you check the browser's network tab

### SOLUTION
we configure wagmi with a dedicated premium rpc.

I pr'd a change to ycrv's wagmi config that uses an rpc configured in .env,
https://github.com/MarcoWorms/ylockers-ui-ycrv/pull/13

the new envar looks like this
NEXT_PUBLIC_RPC_1=https://rpc.ankr.com/eth/0aa3f8c1473421ccea0d723cdf35dcd11fd00d2fe4c85b1145d16be5c73d0039

that rpc is configued on ankr.com in a team account i upgraded to premium and topped up with 50 USDC, or ~2.5M rpc reqs. that's good for a while and the overdraft protection is ~.25M requests.

DM me an email address for access to the ankr team account (I think for team account ankr requires email? not 100% sure)

changes need to be synced w prisma