Break provider-aws up by service

[ulucinar]

Description of your changes

Relevant proposal: crossplane/crossplane#3939
Depends on: crossplane/upjet#194

This PR proposes the following changes according to the proposal crossplane/crossplane#3939:

• Subpackages belonging to each API group is produced. An example is: provider-aws-kms.
• ProviderConfig, ProviderConfigUsage and StoreConfig are part of a config package named provider-aws-config.
• The monolith package (containing all the CRDs and associated controllers) is still produced.
• Each produced package except for the monolith package has the pkg.crossplane.io/provider-family label in its package metadata.
• Each service package except for the config package declares a dependency to the config package.

It also introduces the SUBPACKAGES make variable so that it's possible to build the individual subpackages. An example for building is:

make -j 3 SUBPACKAGES="monolith config ec2" build.all

One can also use the same variable to push those (already built) packages:

make -j 3 SUBPACKAGES="monolith config ec2" BRANCH_NAME=main publish

I have:

• Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

Successfully built and pushed the monolith, config and ec2 subpackages.

Also successfully provisioned and destroyed an ec2.VPC instance using the package .../upbound/provider-aws-ec2:v0.34.0-rc.0.20.ga26202f1.

[ulucinar]

Do we know of a lightweight templating tool that we can quickly integrate into our build pipelines?

[turkenh]

We can use gomplate. It is already available in the build submodule (we may want to move it out of local.mk though).

[ulucinar]

Thanks @turkenh for the suggestion, makes sense to me. Let's proceed as separate manifests for now and once we have the installation of gomplate refactored into somewhere like the k8s_tools.mk, then we can utilize the tool for templating the crossplane.yaml.

[turkenh]

As we discussed offline, we may want to soften the requirement here. Consider the following scenario:

1. Installed provider-aws-ec2:v0.50.0.
2. Config package provider-aws-config:v0.50.0 installed via package manager.
3. Upgraded ec2 package to provider-aws-ec2:v0.51.0
4. Package manager will start failing since the dependency to the config package (>=v0.51.0 is not satisfied unless the config package is upgraded to that version manually.

I believe we don't want to introduce such a constraint and we should instead use >=v0.0.0 here. One caveat, in that case, would be working with rc versions though as they would still bring the latest stable as dependency 🤔

[ulucinar]

/test-examples="examples/ec2/vpc.yaml"

[ezgidemirel]

I have updated the platform-ref-aws configuration with the sub-packages and successfully installed it. There are 160 CRDs installed to the cluster and I could successfully create the cluster claim.