chore: update core OTel deps to v1.0

[rauno56]

Description

Updating OTel deps to the latest versions. For many of them, it's v1.0.

Type of change

• New feature (non-breaking change which adds functionality)
• Internal change (a change which is not visible to the package consumers)
• Change file has been generated (npm run change:new)
• Delete this branch (after the PR is merged)

[codecov-commenter]

Codecov Report

Merging #334 (76ffc7b) into main (e40de73) will not change coverage.
The diff coverage is 100.00%.

❗ Current head 76ffc7b differs from pull request most recent head c59ebe3. Consider uploading reports for the commit c59ebe3 to get more accurate results

@@           Coverage Diff           @@
##             main     #334   +/-   ##
=======================================
  Coverage   93.89%   93.89%           
=======================================
  Files          10       10           
  Lines         344      344           
  Branches       89       89           
=======================================
  Hits          323      323           
  Misses         21       21           

Impacted Files	Coverage Δ
src/options.ts	98.93% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e40de73...c59ebe3. Read the comment docs.

[jtmal-signalfx]

I think this is fine, but shouldn't @opentelemetry/instrumentation have the same supported versions as @opentelemetry/instrumentation-*?

[rauno56]

It doesn't have to. Different instrumentations can use (and as the ecosystem evolves will use) different versions of @opentelemetry/instrumentation to build on for a starter.
We are actually depending on @opentelemetry/instrumentation for the utils and types - little to do with which version of the package instrumentation libs are using.