API version in peer dependencies

[Flarna]

Currently we use a API peer dependency version ^1.0.0 at most locations. Exceptions are locations where a newer API is needed (mostly because of metrics) like in @opentelemetry/instrumentation.

Packages like @opentelemetry/instrumentation-fetch have still ^1.0.0 in their package.json but as it depends also on @opentelemetry/instrumentation. So effective it's ^1.3.0.

Should we move to ^1.3.0 in general? There are no tests which really verify that e.g. 1.0.0 would work in some special setups.

[dyladan]

Hmm didn't think about the transitive 1.3.0 requirement. Yes it probably makes sense to update it to be consistent

[legendecas]

Agreed that transitive dependencies on api should be updated to ^1.3.0 too.