Update opentelemetry SDK versions

[pamelafox]

Purpose

This pull request includes updates to the dependencies in the pyproject.toml and requirements.txt files to ensure compatibility with the latest versions of the OpenTelemetry instrumentation packages. The most important changes involve updating the version constraints and specific versions of various OpenTelemetry packages.

Dependency updates in pyproject.toml:

• Updated opentelemetry-instrumentation-sqlalchemy, opentelemetry-instrumentation-aiohttp-client, and opentelemetry-instrumentation-openai to remove specific version constraints, allowing for more flexibility in dependency resolution.

Dependency updates in requirements.txt:

• Updated opentelemetry-api from version 1.27.0 to 1.30.0.
• Updated opentelemetry-instrumentation from version 0.48b0 to 0.51b0.
• Updated multiple OpenTelemetry instrumentation packages (e.g., aiohttp-client, asgi, dbapi, django, fastapi, flask, openai, psycopg2, requests, sqlalchemy, urllib, urllib3, wsgi) from version 0.48b0 to 0.51b0.
• Updated opentelemetry-sdk from version 1.27.0 to 1.30.0.
• Updated opentelemetry-util-http from version 0.48b0 to 0.51b0.

Does this introduce a breaking change?

When developers merge from main and run the server, azd up, or azd deploy, will this produce an error?
If you're not sure, try it out on an old environment.

[ ] Yes
[X] No

Type of change

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[X] Other... Please describe:

Code quality checklist

See CONTRIBUTING.md for more details.

• The current tests all pass (python -m pytest).
• I added tests that prove my fix is effective or that my feature works
• I ran python -m pytest --cov to verify 100% coverage of added lines
• I ran python -m mypy to check for type errors
• I either used the pre-commit hooks or ran ruff manually on my code.