Ignore latest tags in chart upgrade

[rgee0]

Description

As described in #1086 the chart upgrade command was upgrading latest tags which was undesirable.

This change causes the upgrade command to ignore any images tagged latest.
It also addresses an edge-case around -RC tags which was highlighted by the additional test created in this change.
The k10mulitcluster tool that was disabled has also been removed, so closes #1082

Motivation and Context

• I have raised an issue to propose this change, which has been given a label of design/approved by a maintainer
  Fixes Don't upgrade latest tag via chart upgrade command #1086

How Has This Been Tested?

Functionally tested by using the faasd docker-compose.yaml.
Initially ran chart upgrade on the file as is, and one change was found:

➜  arkade git:(ignoreLatest) ✗ ./arkade chart upgrade -f faasd.yaml -v
2024/06/13 09:37:33 Verifying images in: faasd.yaml
2024/06/13 09:37:33 Found 4 images
2024/06/13 09:37:34 [ghcr.io/openfaas/gateway] 0.27.5 => 0.27.7

This image was then changed to ghcr.io/openfaas/gateway:latest and the command run again:

➜  arkade git:(ignoreLatest) ✗ ./arkade chart upgrade -f faasd.yaml -v
2024/06/13 09:37:50 Verifying images in: faasd.yaml
2024/06/13 09:37:50 Found 4 images

The new test passes as show in the pipeline

No new tool has been added.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Documentation

• I have updated the list of tools in README.md if (required) with ./arkade get --format markdown
• I have updated the list of apps in README.md if (required) with ./arkade install --help

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have signed-off my commits with git commit -s

• I have tested this on arm, or have added code to prevent deployment

[rgee0]

I'm wondering whether it would be better to now use nextTag rather than latestTag in the pre-existing code to avoid confusion around :latest tags

[alexellis]

Approved