Upgrade to opentelemetry-swift-2.x

[williazz]

Describe the bug

Hi I'm from https://github.com/aws-observability/aws-otel-swift and a contributor to https://github.com/open-telemetry/opentelemetry-swift

Would you consider upgrading to opentelemetry-swift-2.x in a major version bump? I'm seeing some reports of folks who are unable to resolve both major versions, and forced to stay on 1.x due to smithy-swift's dependency.

Expected Behavior

Users of smithy-swift should be able to depend on otel-swift-2.x

Current Behavior

Users are reporting unable to build

Reproduction Steps

amplify-swift → aws-sdk-swift 1.6.7 → smithy-swift 0.175.0 → requires opentelemetry-swift 1.x
aws-otel-swift 1.0.0 → requires opentelemetry-swift 2.x

Possible Solution

Possibly upgrade to otel-swift 2.x given that it's been released for sometime now

Additional Information/Context

No response

AWS SWIFT SDK version used

1.67

Compiler and Version used

swiftv6

Operating System and version

n/a

[williazz]

aws-observability/aws-otel-swift#100

[dayaffe]

Hi @williazz, thanks for filing this issue! Looking into this. I believe we can update our OpenTelemetry dependency to 2.x in smithy-swift-opentelemetry. Additionally, as noted in our recent announcement, we'll be removing this dependency from smithy-swift soon and making it an optional, standalone package. Once that's done, it will no longer cause conflicts between amplify-swift and aws-otel-swift unless they are using the tracing feature in the sdk that requires that package.

[williazz]

Amazing! Thanks so much. Removing or upgrading are both valid optoins

[dayaffe]

We plan to do both! smithy-lang/smithy-swift-opentelemetry#6 will merge on 3/10