Leighton Chen

@aabmass This might be a bigger discussion on how we should be handling the new http semantic convention migrations. For now, please hold off on this PR. Will bring this...

From discussion of 07/11/2024 SIG, just an update on what is blocking this PR. Some of the instrumentations that this pr touches still has not been migrated to new semantic...

Resource container was added to our [release script](https://github.com/open-telemetry/opentelemetry-python-contrib/pull/1949) last week. It should be published to pypi as part of our next release cycle.

There was an issue releasing the new version of opentelemetry-resource-detector-container==0.42b0, we are working on it to get it resolved.

Related PyPi issue here: https://github.com/pypi/support/issues/3374 Seems like another case of namesquatting.

I believe we can do a hotfix similar to [this](https://github.com/open-telemetry/opentelemetry-python-contrib/issues/2053#issuecomment-1928485674) so users can have a workaround for now. wdyt @ocelotl ?

I think we need to first answer the question: do we want to capture and handle exceptions and exception information for errors that occur in user supplied hooks? Is span...

@ebracho I agree with the "handling exception" portion, I am just not sure about the "capturing telemetry information" part about the exception itself in the span.

There was an issue releasing the new version of `opentelemetry-instrumentation-aiohttp-server==0.42b0`, we are working on it to get it resolved.

@aabmass I believe we removed them manually from the commit since it was failing the release [build](https://github.com/open-telemetry/opentelemetry-python-contrib/actions/runs/7227861746/job/19696291312). The build fails as soon as an error occurs and the packages that...