snap: add track 'latest' if no track is specified

[russoz]

SUMMARY

When a channel is specified but not using a track, the default track latest is added. the snap list command does that, so this is necessary to match the requested channel with the already installed ones.

See https://snapcraft.io/docs/channels for more details.

A test case has been added to the unit tests to assert that scenario works.

Fixes #6821

ISSUE TYPE

• Bugfix Pull Request
• Test Pull Request

COMPONENT NAME

snap

[ansibullbot]

cc @angristan @vcarceler
click here for bot help

[felixfontein]

This PR needs a changelog fragment :)

[russoz]

Darn, you're always faster than me on these things :-P

[felixfontein]

Looks good to me. If nobody objects by the end of this week, I'll merge.

[patchback]

Backport to stable-6: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply dc0d004 on top of patchback/backports/stable-6/dc0d00452fa6070f01c618ad95f3edc44209af4b/pr-6835

Backporting merged PR #6835 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/ansible-collections/community.general.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-6/dc0d00452fa6070f01c618ad95f3edc44209af4b/pr-6835 upstream/stable-6

4. Now, cherry-pick PR snap: add track 'latest' if no track is specified #6835 contents into that branch:

   $ git cherry-pick -x dc0d00452fa6070f01c618ad95f3edc44209af4b

   If it'll yell at you with something like fatal: Commit dc0d00452fa6070f01c618ad95f3edc44209af4b is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x dc0d00452fa6070f01c618ad95f3edc44209af4b

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR snap: add track 'latest' if no track is specified #6835 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-6/dc0d00452fa6070f01c618ad95f3edc44209af4b/pr-6835

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[felixfontein]

@russoz thanks!

[patchback]

Backport to stable-7: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-7/dc0d00452fa6070f01c618ad95f3edc44209af4b/pr-6835

Backported as #6888

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.