Support for AAD Audience in connection string (for sovereign cloud) & bump in autoconfigure version

[harsimar]

Fix # .
Note: Don't merge until this related change from the autoconfigure module is released.

This PR incorporates connection string parsing changes from the autoconfigure module to use the AAD audience that is either provided via the connection string (or a default audience if that isn't provided). This is applicable for sovereign cloud scenarios where customers may be using AAD auth - the LazyHttpClient would use the provided audience when creating a new http pipeline, and all calls to quickpulse/breeze/profiler would be made with that audience.

Tested in sovereign cloud environment via a local build.

For significant contributions please make sure you have completed the following items:

• Design discussion issue #
• Changes in public surface reviewed
• CHANGELOG.md updated

[harsimar]

This line was added because ConsumptionPlanEnabledTest & RunTimeAttachWithDelayedConnectionStringTest were failing without this check. This raises a few questions ~

1. Are azure functions w/ consumption plan enabled supported in sovereign clouds? If so, would the connection string always be set with some delay? Or is it still possible in azure function consumption plans to not set the connection string with a delay?
2. I noticed in these tests that the connection string is still null by the time the http pipelines are being created. Is there a need to refactor code such that http pipelines shouldn't be created unless the connection string is set to some value, or to be able to handle dynamic config for http pipeline somehow?

[jeanbisutti]

The runtime attachment is related to https://learn.microsoft.com/en-us/azure/azure-monitor/app/java-spring-boot#enabling-programmatically.

The connection string can be configured at runtime (programmatically) with -javaagent or the runtime attachment.

With Azure function, the connection string retrieval is delayed:

ApplicationInsights-Java/agent/agent-tooling/src/main/java/com/microsoft/applicationinsights/agent/internal/init/AzureFunctionsInitializer.java

Line 90 in d89b256

runtimeConfig.connectionString = getAndLogAtDebug("APPLICATIONINSIGHTS_CONNECTION_STRING");

About question 1, I don't know.

About 2, it may have several options. The place where the connection string is set at runtime (programmatic configuration or Azure function):

ApplicationInsights-Java/agent/agent-tooling/src/main/java/com/microsoft/applicationinsights/agent/internal/init/RuntimeConfigurator.java

Line 121 in d89b256

updateConnectionString(runtimeConfig.connectionString);