Integrate azure-sdk-bom in a non-conflicting manner

While working on CAMEL-18451 I ran into a conflicting Azure dependency issue. To reproduce it just add the following dependency to camel-azure-eventhubs POM without any other additional changes whatsoever:

<dependency>
    <groupId>com.azure</groupId>
    <artifactId>azure-identity</artifactId>
    <version>${azure-identity-version}</version>
</dependency>

and the integration test execution as mentioned here will hang forever until it time outs through the maven-failsafe-plugin.

This is because currently we have the following dependency versions on the main branch:

<azure-eventhubs-version>5.11.2</azure-eventhubs-version>
<azure-identity-version>1.5.1</azure-identity-version>

The currently used azure-eventhubs version belongs to the BOM:

https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.1

Whereas the current azure-identity version belongs to:

https://mvnrepository.com/artifact/com.azure/azure-sdk-bom/1.2.2

Each having potentially incompatible / non-matching own transitive dependency versions causing some sort of deadlock behaviour at runtime as explained above.

We better need to make sure that whatever azure-XXX dependencies we have belong to the same azure-sdk-bom version.

I think it's possible to make use of azure-sdk-bom BOM in a non-conflicting manner.