fix cosmos auditing circular ref

[saragluna]

Description

Fix #35736. The regression was brought in #34878. However, this fix is not ideal, because it will create a new instance of CosmosMappingContext and injects it into the auditingHandler.

The circular reference is caused by our CosmosTempate references the auditingHandler directly, which should be propagated via the event to do the auditing.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

azure-spring-data-cosmos
spring-cloud-azure-autoconfigure

[Netyyyy]

/azp run java - spring - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Netyyyy]

LGTM.

[kushagraThapar]

Thanks for the fix @saragluna - shouldn't we need to fix this on main branch as well?