Generate namespaced managed resources

[jbw976]

Description of your changes

This PR continues the work from draft PR #1689 that @negz started. It essentially updates this provider to start generating namespaced managed resources in addition to cluster scoped ones, which will be featured heavily in the current proposal of Crossplane v2.

This should not be taken as a final product. This is a practical update to this provider as a proof of concept for what we think a provider could look like in Crossplane v2. There are many short cuts taken, it is not production ready, and we are very open to feedback to change directions or improve the architecture.

The work in this PR should be merged into the new crossplane-v2 branch, which is based on commit 1ecd9cb, the latest commit when we started this work. We will need to rebase this effort in the future to include latest changes from main, but that should not block this PR.

I have:

• Read and followed Crossplane's contribution process.
• Run make reviewable to ensure this PR is ready for review.

General steps this PR has taken

The following list describes the general process that was taken to update this provider to support namespaced MRs:

• update to latest upjet version that supports namespaced resources
• duplicate content into both cluster and namespaced copies and make some minor updates for api groups and import paths
  • config, apis, controllers
• remove all legacy conversion/migration logic, because only the latest version needs to be supported
• update the provider main.go template to setup both cluster and namespaced apis and controllers
• update code generation comment markers to run on both cluster and namespaced types
• update the generator cmd to init both cluster and namespaced config to pass to code gen pipeline
• manually copy and update the handful of manual api and controller files to namespaced dirs

How has this code been tested

Besides generating, building and publishing successfully, this code has also been tested manually by installing the config, s3, rds, and ec2 packages into a control plane, then creating both cluster scoped and namespaced S3 buckets. Ex.:

❯ { head -n 1; grep '^buckets '; } < <(kubectl api-resources)
NAME                                        SHORTNAMES   APIVERSION                            NAMESPACED   KIND
buckets                                                  s3.aws.upbound.io/v1beta2             false        Bucket
buckets                                                  s3.m.aws.upbound.io/v1beta1           true         Bucket

❯ k get managed -A
NAMESPACE   NAME                                               SYNCED   READY   EXTERNAL-NAME             AGE
            bucket.s3.aws.upbound.io/crossplane-bucket-tmm54   True     True    crossplane-bucket-tmm54   21s

NAMESPACE   NAME                                                 SYNCED   READY   EXTERNAL-NAME             AGE
xp          bucket.s3.m.aws.upbound.io/crossplane-bucket-mhv6k   True     True    crossplane-bucket-mhv6k   18s

[jbw976]

I lost the ability to push to @negz's fork/branch when I opened this new PR with my as the author. I'll open a new PR from my fork.