[Azure] Supply guid from django_guid as the correlationId on storage calls

[jasonzio]

If the django-guid package is installed and django_guid.set_guid() has been called, fetch that guid and apply it as the correlationId for all Azure storage API calls. If the module isn't importable or no guid has been set, don't supply a correlationId.

While the test environment requires the django-guid package, the runtime environment need not have that package installed.

[hartungstenio]

Is committing to django-guid for this something we want? What if people have other means of generating a Correlation ID (django-log-request-id or OpenTelemetry).

Maybe simple adding a make_headers method to the Azure Storage, and allowing users to override it using any solution they want, would be a simpler solution, without committing to any individual package.

[daviddavis]

There's PRs open that add a request_options method to do this.

• This one will use django-guid if it's installed - Add AZURE_REQUEST_OPTIONS setting (#1179) #1468
• This one just adds the method but doesn't use django-guid at all - Add AZURE_REQUEST_OPTIONS setting (#1179) #1467

[sdherr]

@hartungstenio We are still very interested in getting one of the PRs that resolves this issue merged, please let me know what changes you require. Currently there is no way to pass through the per-operation keyword args to the Azure Storage client, except for timeout which is already explicitly added on each request. Merging one of the PRs that create the AZURE_REQUEST_OPTIONS setting gives users the ability to set these per-request options, if they care about them.

It is my personal opinion that using django-guid if it is installed is the most-correct thing to do, and so #1468 is the best candidate. However if you don't want to be tied to django-guid at all then #1467 is also acceptable.