test: add minor version upgrade to the upgrade matrix

[jessesimpson36]

Which problem does the PR fix?

related to
#959
https://github.com/camunda/team-distribution/issues/449
https://github.com/camunda/team-distribution/issues/450

What's in this PR?

Extra jobs that test scenarios like upgrading from latest 8.6 -> 8.7 or latest 8.3 -> 8.4

I separated this patchset by 2 commits:

The first commit is the minimum amount of lines changed needed to get the functionality of testing this extra upgrade-job going from the last minor release to the current chart.

The 2nd commit takes the 5 JQ expressions and converts them to a golang script. IMO this is better because it's more flexible, gives us a lot more structured access to the metadata, and each individual line of code holds less weight and is more easily testable.

Checklist

Please make sure to follow our Contributing Guide.

Before opening the PR:

• In the repo's root dir, run make go.update-golden-only.
• There is no other open pull request for the same update/change.
• Tests for charts are added (if needed).
• In-repo documentation are updated (if needed).

After opening the PR:

• Did you sign our CLA (Contributor License Agreement)? It will show once you open the PR.
• Did all checks/tests pass in the PR?

[jessesimpson36]

The repetitive job logic is now replaced with extra JQ expressions for making the matrix. Nice thing about that is now we don't have to look at dozens of skipped jobs.

[jessesimpson36]

Before merging, we will need to remove the test annotation I added into each Chart.yaml. I'm keeping it for now so we can have tests running on each minor version.

[aabouzaid]

I write this just to avoid GH pinging me about this PR.
We already discussed changing the approach a bit ... so I will wait for the updated PR.