Uptest family providers

[ulucinar]

Description of your changes

Depends on: upbound/build#241

Currently when an e2e test is triggered in upbound/provider-aws, the test is run with the monolithic provider (upbound/provider-aws) package built from the feature branch.

This omits the family resource providers (not a problem from the resource configuration validation perspective because both the monolith and the corresponding resource provider utilize the same resource configuration) but the built family resource package itself is not tested).

Another issue that's the main motivation of the proposed changes in this PR is that the number of CRDs installed with the monolithic package cause noise in the tests (pod restarts, timeouts at various levels, etc.).

This PR proposes to switch to the family resource providers when running uptests in this repo.

I have:

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

How has this code been tested

Tested locally by running:

...
export UPTEST_EXAMPLE_LIST="examples/iam/role.yaml,,examples/iam/user.yaml,,examples/iam/policy.yaml,,examples/ec2/vpc.yaml,"
make e2e

Note: Common dependencies in the above example manifest list may cause testing issues unrelated to this PR. cc. @turkenf, who also confirmed similar findings with the dependencies. We've long been discussing a shared catalog of dependencies from which dependencies can be injected into the dependent example manifests with the help of an uptest preprocessor. This is not in the scope of this PR as mentioned.

Also tested with the following uptest runs:

• https://github.com/upbound/provider-aws/actions/runs/6382820488: Single API group (ec2)
• https://github.com/upbound/provider-aws/actions/runs/6383043228: Multiple API groups (ec2, iam), one group per file
• https://github.com/upbound/provider-aws/actions/runs/6383230674: Multiple API groups (ec2, iam, sfn), where a single example manifest file contains the two groups iam and sfn:

...
17:10:35 [ .. ] Building and deploying resource providers for the short API groups: config,ec2,sfn,iam,
...
17:11:19 [ .. ] Batch processing smaller provider packages for: config ec2 sfn iam 
...
17:12:47 [ OK ] deploying provider package provider-aws-config v0.0.0-3.gcc29e5c
...
17:13:02 [ OK ] deploying provider package provider-aws-ec2 v0.0.0-3.gcc29e5c
...
17:13:26 [ OK ] deploying provider package provider-aws-sfn v0.0.0-3.gcc29e5c
...
17:13:43 [ OK ] deploying provider package provider-aws-iam v0.0.0-3.gcc29e5c
...

Also verified the metadata of the provider packages produced by:

make SUBPACKAGES="iam config" BRANCH_NAME=main XPKG_REG_ORGS=index.docker.io/ulucinar build.all publish

[ulucinar]

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

[ulucinar]

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

[ulucinar]

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

[ulucinar]

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

[ulucinar]

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

[ulucinar]

/test-examples="examples/ec2/vpc.yaml,examples/iam/role.yaml"

[ulucinar]

/test-examples="examples/ec2/vpc.yaml,examples/sfn/statemachine.yaml"

[sergenyalcin]

Thanks @ulucinar LGTM!