fix: Azure API throttling error & incorrect page size request for workflows

[0xffhh]

This PR fixes two issues which only seem to occur in (very) large environments.

1. The current AzureHound version results in a lot of "The request was throttled." error messages from the Azure API. The root cause seems to be the collection command "list-storage-containers" which then cascades into the same throttling for other collection methods. See also here: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#storage-resource-provider-limits. By tuning down the concurrency of this storage command, all other throttling issues seem to disappear. This issue is also reported already as issue "The request was throttled" errors when using AzureHound #7 .
2. The following error occurs when collecting workbooks:
   Error: map[error:map[code:InvalidTopInQueryString message:The value '2147483647' was provided for top; a value less than or equal to '1000' must be provided.]]
   So changed the value to 1000, got a similar error. Changed to 999 to compensate for an off-by-one on Azure's side, but still got the same error
   Error: map[error:map[code:PageSizeLimitExceeded message:The requested page size of '999' exceeds the allowed limit of '100'.]]
   Setting the value to 100 fixes the issue. This is not a permanent fix, as obviously there could be more than 100 workbooks in that subscription. However, at least it collects some data for now, until there is a more permanent fix.

Results for comparison: the rolling version without this patch collects an output file of 4.2GB after this patch the output is 31GB.

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[0xffhh]

I have read the CLA Document and I hereby sign the CLA