Support Emitting Application Insights Custom Events

[rajkumar-rangaraj]

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

Summary:
This PR enables the emission of Application Insights Custom Events based on OpenTelemetry LogRecords.

Implementation Details:

• If the microsoft.custom_event.name attribute is found in the LogRecord:
• The SDK emits a Custom Event.
• The Name of the event is set to the value of microsoft.custom_event.name.
• If the attribute is not present, the LogRecord follows its default behavior.

Changes Made:

• Implemented logic for detecting and processing microsoft.custom_event.name.
• Added unit tests to ensure correct behavior.

How to Test:
Emit a LogRecord with the microsoft.custom_event.name attribute.
Verify that the telemetry is emitted as EventTelemetry with the expected name.

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

API changes are not detected in this pull request.