Adding message IDs to diagnostic logging

[jeremydvoss]

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 API spec, a link to the pull request containing these API spec changes should be included above.

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.

[Copilot]

Pull Request Overview

This PR adds new message IDs to the diagnostic logging system in the Azure Monitor OpenTelemetry SDK. The change introduces several new diagnostic message identifiers for better categorization and tracking of different error and warning scenarios.

• Adds new message IDs for backoff-related scenarios (4301-4303)
• Adds a new exception message ID (4404)