Remove azure-identity IdentityClientBase runtime initialization native configuration

[JiriOndrusek]

After upgrade of azure-identity to 1.7.0, native build of extension azure-eventhubs and azure-storage-blob fails with

 org.graalvm.compiler.java.BytecodeParser$BytecodeParserError: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: Detected an instance of Random/SplittableRandom class in the image heap. Instances created during image generation have cached seed values and don't behave as expected.

Problem is caused by this line of code.

Workaround - disabled native build for azure-eventhubs, azure-storage-blob and azure-grouped test.

With proper fix, please enable native profiles again.

[ppalaga]

In azure-identity 1.7.0, they moved the RANDOM field from com.azure.identity.implementation.IdentityClient to com.azure.identity.implementation.IdentityClientBase. I guess we need to produce a RuntimeInitializedClassBuildItem for IdentityClientBase in AzureStorageBlobProcessor.

Anyway, I have filed Azure/azure-sdk-for-java#32744 . Let's see whether Azure SDK team is willing to stop instantiating java.util.Random in the static initializer.

[jamesnetherton]

I registered IdentityClientBase for runtime initialization in 09d9d4d and restored the native testing.

Looks like Azure/azure-sdk-for-java#32744 is fixed already. So we can revert the change when we upgrade to the next azure-identity release.