Breaking Change in v2.3

### What happened?

Why was apis/common (re-)moved in v2.3.0? That is a breaking change in a minor version.
This change is leading to significant problems in the entire ecosystem. The crossplane-runtime and any providers can only be upgraded together, since otherwise the providers would try to consume the removed types and dependencies updates/builds would fail.

Most providers do not suport >=v2.3.0 yet, but upbound/provider-aws does, although only by pinning an unreleased upjet version, which is also a problem, although a separate one.

This situation prevents projects from upgrading any component independently and blocks adoption of new features until all providers are migrated to >=v2.3.0 at the same time.

How could this happen?

Start by comparing the apis/common package between the pre-v2.3.0 and v2.3.0 releases, then trace how crossplane-runtime and provider dependencies consume its types. Review the compatibility impact across providers and the stated v2.3.0 migration constraint. Done means the breaking-change cause and a supported independent upgrade path are established or the incompatibility is corrected.

Written by the indexing model from the issue text.