[azure] Normalize durationMs to long across Azure integrations

## Context

Some Azure services generate the `durationMs` field with a string value (`"durationMs": "0"`) instead of a long value (`"durationMs": 0`), as implied by the [common schema](https://learn.microsoft.com/en-us/azure/azure-monitor/platform/resource-logs-schema#top-level-common-schema), and explicitly stated in some log categories docs like [aadprovisioninglogs](https://learn.microsoft.com/en-us/azure/azure-monitor/reference/tables/aadprovisioninglogs#columns).

## Goal

Make sure all Azure logs-focused integration always convert the `durationMs` to `long` before sending the log event to ES.

## Impact

Not sending the `durationMs` values with the correct values can create mapping errors and deteriorate the ingest experience.