Use more or better RPC provider

[volovyks]

Description

Now our system is failing each time RPC is experiencing issues. Not sure if we want to run our own node now, we can try a simpler solution for now.

Providers: https://docs.near.org/api/rpc/providers
https://www.lavanet.xyz/get-started/near manage underlying RPC operators and route traffic to ones that are working well

[auto-mausx]

Lava does load balance between available services, so I think the should be the primary, but I think we should still code some resilience into the system. Maybe have an array of provider URLs that can be rotated against when a 5XX or 4XX error is produced a certain number of times?

[volovyks]

It was decided to stick with FastNEAR for now. RPC provider rotation can be added later, not a blocker to close this.