Updates dependencies to get us pretty close to current

[tnthornton]

Description of your changes

It's been a long time since dependencies were updated in this repo. Some of the consequences of that are:

• [x] The crossplane/crossplane dependency hasn't been updated since 1.6 resulting in issues such as:

  • 329

• [x] Any security issues that may have cropped over the last "months" time would remain unresolved.
• [x] The general PR, as seen here, is much larger changeset than we'd tend to like.

The overarching goal of this PR is to get us roughly caught up on the crossplane/crossplane dependency which results in a cascade affect of the other dependencies needing to be updated.

In addition:

• The minimum Go version is being updated to 1.20 (which has affects on the GolangCI Lint version).
• The build submodule is also updated.

Fixes #329

I have:

• [X] Read and followed Upbound's contribution process.
• [x] Run make reviewable to ensure this PR is ready for review.

How has this code been tested

1. Basic validation: make build test reviewable
2. More extensive tests are in progress:
   • [X] xpkg APIs, ensuring above linked issues are resolved.
   • [x] xpls still works the way it did prior to this update

Testing xpls

1. make build
2. move up into terminal path.
3. Check version

   up --version
   v0.18.0-rc.0.11.g6bceab2

   See below screenshots, prior functionality appears to continue to work

Testing xpkg commands

a. Checking if #329 is resolved

1. Followed repro steps in #329 and ended up with an ezgi-platform-ref-gcp.xpkg file.
2. Using up, ran the following command to extract the package up xpkg xp-extract --from-xpkg ezgi-platform-ref-gcp.xpkg
3. Used gzip to uncompress the resulting out.gz: gzip --uncompress out.gz
4. Opened the out file, then searched for status.atProvider.id and found:

   - fromFieldPath: status.atProvider.id
     policy:
       fromFieldPath: Required
     toFieldPath: status.gke.project
     transforms:
     - string:
         regexp:
           group: 1
           match: projects\/(.+)\/serviceAccounts\/.*
         type: Regexp
       type: string
     type: ToCompositeFieldPath

b. Verified that I can push xpkg to registry

up xpkg push xpkg.upbound.io/taylor/tt-test:v0.0.1 -f ezgi-platform-ref-gcp.xpkg
xpkg pushed to xpkg.upbound.io/taylor/tt-test:v0.0.1

c. Verified that I can pull that xpkg into a control plane

[kubedebug] / # cat c.yaml
apiVersion: pkg.crossplane.io/v1
kind: Configuration
metadata:
  name: platform-ref-gcp
spec:
  package: xpkg.upbound.io/taylor/tt-test:v0.0.1

[kubedebug] / # kubectl get providers
NAME                                     INSTALLED   HEALTHY   PACKAGE                                                          AGE
crossplane-contrib-provider-helm         True        True      xpkg.upbound.io/crossplane-contrib/provider-helm:v0.15.0         5m35s
upbound-provider-aws                     True        Unknown   xpkg.upbound.io/upbound/provider-aws:v0.36.0                     5m52s
upbound-provider-family-gcp              True        True      xpkg.upbound.io/upbound/provider-family-gcp:v0.33.1              5m11s
upbound-provider-gcp-cloudplatform       True        True      xpkg.upbound.io/upbound/provider-gcp-cloudplatform:v0.33.0       5m32s
upbound-provider-gcp-compute             True        True      xpkg.upbound.io/upbound/provider-gcp-compute:v0.33.0             5m29s
upbound-provider-gcp-container           True        True      xpkg.upbound.io/upbound/provider-gcp-container:v0.33.0           5m23s
upbound-provider-gcp-servicenetworking   True        True      xpkg.upbound.io/upbound/provider-gcp-servicenetworking:v0.33.0   5m19s
upbound-provider-gcp-sql                 True        True      xpkg.upbound.io/upbound/provider-gcp-sql:v0.33.0                 5m15s

[kubedebug] / # kubectl get providerrevisions
NAME                                                  HEALTHY   REVISION   IMAGE                                                            STATE    DEP-FOUND   DEP-INSTALLED   AGE
crossplane-contrib-provider-helm-503c3591121b         True      1          xpkg.upbound.io/crossplane-contrib/provider-helm:v0.15.0         Active                               5m30s
upbound-provider-aws-3f7547b28ca6                               1          xpkg.upbound.io/upbound/provider-aws:v0.36.0                     Active                               5m48s
upbound-provider-family-gcp-b0fb8e3d4a7a              True      1          xpkg.upbound.io/upbound/provider-family-gcp:v0.33.1              Active                               5m5s
upbound-provider-gcp-cloudplatform-78133325933e       True      1          xpkg.upbound.io/upbound/provider-gcp-cloudplatform:v0.33.0       Active   1           1               5m27s
upbound-provider-gcp-compute-308b9eb8c1d3             True      1          xpkg.upbound.io/upbound/provider-gcp-compute:v0.33.0             Active   1           1               5m24s
upbound-provider-gcp-container-fbc4b73cd0e7           True      1          xpkg.upbound.io/upbound/provider-gcp-container:v0.33.0           Active   1           1               5m18s
upbound-provider-gcp-servicenetworking-3b85e9b62814   True      1          xpkg.upbound.io/upbound/provider-gcp-servicenetworking:v0.33.0   Active   1           1               5m14s
upbound-provider-gcp-sql-d88e7407bac4                 True      1          xpkg.upbound.io/upbound/provider-gcp-sql:v0.33.0                 Active   1           1               5m10s

[AlainRoy]

LGTM! I'll wait to approve until you test, but it looks reasonable.

My only concern is about what happens for new releases of Crossplane. Will it be a lot of work to update the vendored code? Would it help to document anything about the process you followed to do the update, or is just something that we need to work through?

[tnthornton]

My only concern is about what happens for new releases of Crossplane. Will it be a lot of work to update the vendored code? Would it help to document anything about the process you followed to do the update, or is just something that we need to work through?

It's incredibly unclear what the LOE is to update the next time around. Regarding documentation, I don't really know what to document:

• I updated a dependency.
• Fixed compilation errors.
• Copied code over and tore out things that "we didn't need". Still TBD if that plan worked.

[AlainRoy]

My only concern is about what happens for new releases of Crossplane. Will it be a lot of work to update the vendored code? Would it help to document anything about the process you followed to do the update, or is just something that we need to work through?

It's incredibly unclear what the LOE is to update the next time around. Regarding documentation, I don't really know what to document:

* I updated a dependency.

* Fixed compilation errors.

* Copied code over and tore out things that "we didn't need". Still TBD if that plan worked.

OK, that's cool. No need to do anything to document it.

[AlainRoy]

Should we do a new release of up in the near future?

[tnthornton]

Should we do a new release of up in the near future

That makes sense to me. Maybe sometime next week so that we can at the very least get fixes for #329 out.

[phisco]

@jastang I don't think we support multiple releases, looking at https://github.com/upbound/up/tags it looks like we are always going forward with versions, so nothing to backport to