Publish major version (only) tag pointing at the latest build for a major node version

[Royston-Shufflebotham-i2]

In the same way that you already republish the, for example, 18.10 tag when you publish each of the 18.10.1, 18.10.2, ... images, which then gives a tag pointing at the latest v18.10.x image, it would be really helpful to have a plain '18' tag that points at the latest v18.x.y image.

This would enable us to have a build that tests our published component against the latest v14, v16, v18, etc images so that we get an early warning if a new version of Node is released that causes problems with our component. Right now, we'll have to keep manually bumping the minor versions for each major version mentioned in our workflow.

[Gobd]

Wanted to check on this. I think this is important just like the official Node docker image publishes things like 18-alpine so I can easily get security updates without having to bump the version it would be nice the cimg images had the same.