Usage of github.com/upbound/provider-aws/apis/s3/v1beta2 is preventing us from upgrading provider-aws

[awprice]

What happened?

The usage of github.com/upbound/provider-aws/apis/s3/v1beta2 within https://github.com/crossplane/function-sdk-go/blob/main/resource/composed/composed_test.go is preventing us from upgrading github.com/upbound/provider-aws in our function to v2

How can we reproduce it?

• Use https://github.com/crossplane/function-template-go to create a function
• Add a dependency on https://github.com/crossplane-contrib/provider-upjet-aws, but specifically the v2 version, which includes both cluster and namespaced types
• Encounter the following error from go mod tidy:

github.com/crossplane/function-sdk-go/resource/composed tested by
	github.com/crossplane/function-sdk-go/resource/composed.test imports
	github.com/upbound/provider-aws/apis/s3/v1beta2: package github.com/upbound/provider-aws/apis/s3/v1beta2 provided by github.com/upbound/provider-aws at latest version v1.23.0 but not at required version v1.23.1-0.20250811133028-44afb1a357e3

What environment did it happen in?

Crossplane version: v2

[awprice]

Cause of this is because of the change in paths for the types/structs in the V2 providers.

I'm happy to raise a PR to use the V2 provider with the new path, but then I think this will cause issues with users of this SDK that still want to use the V1 providers.

Ideally I think the function SDK doesn't import any providers, allowing users to use any version of providers.