[CSPM] [Azure] [SDH] Timeout on Azure fetchers

[moukoublen]

Describe the bug
Azure fetchers in accounts with large number of resources take more time than anticipated and exceed the timeout in cloudbeat internal fetchers handling that is hardcoded to 20 mins.

Preconditions
CSPM Azure is a subscription with a large number of resources.

Potential Solutions
We should either increase the hardcoded fetcher timeout to e.g. 3 hours (it seems there is no reason for less since the cycle is usually 24h) [quick fix].

or

Change the approach entirely and not limit each fetcher with a standalone timeout, but instead, use a context with a timeout from the beginning of the cycle + cycle time.

[orouz]

the second approach sounds better. i think we should utilize period (from cloudbeat config) and let the fetchers take as much time as the period allows.