Upgrade from the azure-storage-blob-go SDK to the azure-sdk-for-go SDK

[LasseHels]

azure-storage-blob-go has been superseded by the azure-sdk-for-go, and is no longer being actively maintained.

Upgrading to azure-sdk-for-go is a prerequisite for at least one task (#2705), and will fix at least one bug (#2129):

• Correctly implement VersionedReaderWriter on Azure #2705
• [Ingester] Intermittent KubePersistentVolumeFillingUp alerts #2129

[LasseHels]

I'm actively working on this in a fork. Thus far, it seems like the API of the new SDK is pretty similar to the old, and I have not run into major issues. That said, I've not ran any E2E tests yet, so there may be problems waiting for me. I've updated functionality of the azure.readerWriter to use the new SDK, and am in the process of verifying that unit tests are still testing the correct behaviour, and passing when they should.

https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/storage/azblob/migrationguide.md contains a brief overview of the major changes between the two SDKs.

I don't fully understand the different ways that Tempo can connect to Azure Blob Storage, and I am currently using azidentity.NewDefaultAzureCredential in the else authentication branch (i.e. the branch that doesn't use shared key credential). This is probably not what we want to do, and I'll revisit this when I have the rest of the functionality in place.