Pinned OpenTelemetry versions (aiohttp-client, httpx) are outdated and block upgrades

[omgMath]

(Copied from #42117 with some modifications)

Is your feature request related to a problem? Please describe.
I'm currently using azure-monitor-opentelemetry in a project that also relies on the opentelemetry-instrumentation-aiohttp-client and httpx libraries. However, I'm unable to upgrade past version 0.61b0 of those instrumentations because azure-monitor-opentelemetry has them pinned.

These versions are several months old now, and since then there have been multiple releases with important bug fixes and improvements in the OpenTelemetry ecosystem.

Describe the solution you'd like
Can you please update the version constraints - either bump to at least 0.61b0 or allow a looser version spec (e.g., >=0.61b0, <0.65)?

Describe alternatives you've considered

• Hacking around those dependency pins

Additional context
Let me know if there's a compatibility or stability reason for the current pinning.

[kashifkhan]

Thank you for the feedback @omgMath . Ive routed this to the team that can help you further.

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @hectorhdzg @JacksonWeber @jeremydvoss @lzchen @MSNev @rads-1996.

[rads-1996]

@omgMath We are working on releasing a version of the distro that relies on the latest dependencies. I will update this issue once we have a new release you can use. We are waiting for logs to be stabilized in upstream OTEL and are pushing actively towards the initiative,