feat: add documentation on useAzureMonitorSdk feature flag (#62)

Co-authored-by: Tom Kerkhove <kerkhove.tom@gmail.com>

Author: hkfgo

docs/scraping/runtime-configuration.md

@@ -47,6 +47,7 @@ azureMonitor:
     informationLevel: Basic # Optional. Default: Basic
     isEnabled: false # Optional. Default: false
   integration:
+    useAzureMonitorSdk: true # Optional. Default: true
     history:
       startingFromInHours: 24 # Optional. Default: 12
 telemetry:
@@ -351,6 +352,7 @@ The behavior of this can be configured to fit your needs:
  API. (Default: `false`)
 - `azureMonitor.integration.history.startingFromInHours` - Defines the amount of hours Promitor will use to define the starting point of the time window used for metric queries.
   - As an example, the default is 12 hours which means Promitor will fetch all metrics between now - 12 hours and now to find a matching metric. Typically this window can be very small but Promitor provides a margin by default to prevent problems for long aggregation periods. (Default: `12`)
+- `azureMonitor.integration.useAzureMonitorSdk` - In the newest release of Promitor, integration with Azure Monitor will use [Azure.Monitor](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/monitor/Azure.Monitor.Query) package under Azure SDK for .NET by default. This migration was needed because the [original SDK](https://github.com/Azure/azure-libraries-for-net) has been deprecated since 2022. 
 
 Example:
 
@@ -360,6 +362,7 @@ azureMonitor:
     informationLevel: Basic # Optional. Default: Basic
     isEnabled: false # Optional. Default: false
   integration:
+    useAzureMonitorSdk: true # Optional. Default: true
     history:
       startingFromInHours: 24 # Optional. Default: 12
 ```