Add setAzureMonitorOptions() to Configuration

[huang-julien]

Hello 👋

I'm coming from applicationinsights 2 and i like that we still have a shim in v3 while moving to OTEL.

This PR aims to improve a bit the DX by adding a setAzureMonitorOptions() static method to Configuration .
The reason is that those who upgraded from v2 to v3 may still use setup() which returns the Configuration class. In order to modify AZure Monitors options, users would have to do something like:

const configuration = setup('connection-string')
defaultClient.config.azureMonitorOpenTelemetryOptions = { /** ... **/ }
configuration.start()

this PR would allow to do this instead

setup('connection-string')
  .setAzureMonitorOptions({ /** ... **/ })
  .start()

[JacksonWeber]

@huang-julien Just so I can understand your use-case a little better. You're adopting modifying the azureMonitorOpenTelemetryOptions directly, so I'm interested in why you're not migrating to the Azure Monitor OpenTelemetry distro. Are you just using the shim for access to the track APIs?

[huang-julien]

Yup I am. I'm actually the maintainer of nitro-applicationinsights and nuxt-applicationinsights.

The shim is very conveniant for SSR frameworks as it provide quasi-identical methods between appinsights node and appinsights web which allows for devs ( in frameworks such as Nuxt) to be able to call track* methods through a single property without having to care about server-side/client-side code.

[Copilot]

Pull Request Overview

A concise update to improve developer experience for upgrading from v2 to v3 by adding a static method to set Azure Monitor options on the global configuration.

• Adds a static method setAzureMonitorOptions() to modify Azure Monitor OpenTelemetry options.
• Provides chaining support to simplify configuration by returning the Configuration class.