[Monitor Opentelemetry] Add 3.13 and 3.14 support

[hectorhdzg]

Description

Add support for Python 3.13 and 3.14 in azure-monitor-opentelemetry and azure-monitor-opentelemetry-exporter

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.

[lzchen]

Is azure-sdk already testing 3.14? Could you link to it if so?

[Copilot]

Pull request overview

This PR adds Python 3.13 and 3.14 support to two Azure Monitor OpenTelemetry packages by updating package metadata and documentation.

Key Changes:

• Added Python 3.13 and 3.14 to PyPI classifiers in setup.py for both packages
• Updated CHANGELOG.md files to document the new version support

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
sdk/monitor/azure-monitor-opentelemetry/setup.py	Added Python 3.13 and 3.14 classifiers to package metadata
sdk/monitor/azure-monitor-opentelemetry/CHANGELOG.md	Documented Python 3.13 and 3.14 support in Other Changes section
sdk/monitor/azure-monitor-opentelemetry-exporter/setup.py	Added Python 3.13 and 3.14 classifiers to package metadata
sdk/monitor/azure-monitor-opentelemetry-exporter/CHANGELOG.md	Documented Python 3.13 and 3.14 support in Other Changes section

---

The changes in this PR are straightforward and consistent. Both packages already have python_requires=">=3.8" in their setup.py files, which is compatible with the newly declared Python 3.13 and 3.14 versions. The CHANGELOG entries are properly placed in the "Other Changes" section for the upcoming unreleased versions. No issues were identified with the proposed changes.

[JacksonWeber]

LGTM