Refactor provider-proxy to accept REST_API_NODE_URL

[stalniy]

Why

Right now, all backend services expect RPC_NODE_ENDPOINT (write) env variable and use this REST_API_NODE_URL(read) to talk to blockchain but provider-proxy relies on local packages/net package data (which is fetched on every commit from https://github.com/akash-network/net). And this makes it impossible to provide a custom proxy option. Right now, we want to switch provider-proxy to use our own rpc proxy which ensures that request is delivered to healthy blockchain node

What

1. Add REST_API_NODE_URL env variable to provider-proxy
2. Add .env.sample put the value from https://github.com/akash-network/net/blob/main/sandbox-2/meta.json#L52C21-L52C26 and a link to https://github.com/akash-network/net in comment to look for other values
3. Add .env.mainnet and .env.sandbox with corresponding values from https://github.com/akash-network/net
4. Use REST_API_NODE_URL and remove chainNetwork and network parameter from proxy requests https://github.com/akash-network/console/blob/main/apps/provider-proxy/src/utils/schema.ts#L26
5. Adjust deploy-web to create a new instance of ProviderProxyService when network changes (use networkStore.selectedNetworkId). Network change happens with page reload. Add corresponding env variables like it's done for api https://github.com/akash-network/console/blob/main/apps/deploy-web/env/.env#L16-L18

[stalniy]

@jzsfkzm would you like to work on this?

[stalniy]

this one cannot be merged without preparing #2190 otherwise we won't be able to deploy provider-proxy for some time

[jzsfkzm]

@jzsfkzm would you like to work on this?

sure, assign it to me please