Update SG queries on Cron job to use pagination about rain-studio

[hardyjosh]

@NanezX I think it makes sense to check the most recent block/timestamp for any fetched data and start from there.

[NanezX]

Okay, the cron job has been running since yesterday and the average execution time is not to my liking.

Although the code is functional, it needs optimization as naturally the subgraph data will increase (and we will add more subgraphs in the future).

So the best and logical solution is created a new table on the supabase database, maybe called networks or other name. Here we can store relevant information related for each network that we can use on studio. My first thought of this is the following table:

ID (uuid)*	created_at (timestamp)*	chainId	lastBlockSG	interpreterUrlSG
UUID generated	Time when the row was added	chain Id for the network	Last block checked by the cronjob on the the subgraph(s) by this chain ID	URL endpoint for interprerter subgraph on the give chain ID

It is very basic and only intended to meet the cronjob requirements, but of course this allow us to add more columns if we need. @hardyjosh

[NanezX]

@NanezX I think it makes sense to check the most recent block/timestamp for any fetched data and start from there.

Ok cool, then I'll leave the PR and ticket open to change the code after closing the selection for contracts