tools/geneos: allow custom release version for `--override`

[pgalbavy-itrs]

If, for example, we want to install a copy of a netprobe release so that we can use setcap on the binary we might try to use geneos package install --override probe:7.5.0+setcap and then use a new base version like active_setcap to point to it.

At the moment this is not possible for a number of reasons:

1. The check for a suitable version in archives.go is too strict and limits the version string to d.d.d style
2. When checking for latest versions and doing manual version updates with geneos package update -V 7.5.0 this will match the custom version as the general test for el8 and el9 consumes the custom string

Changes required in addition to addressing the above may also include a way to match exact versions in places -V/--version can be used, which at the moment find the "latest" match. Also, when using --override should the user be required to supply a base version (--base active_setcap) explicitly to protect against clashes?

In early testing it also appears geneos package delete doesn't work with custom versions

[pgalbavy-itrs]

Having addressed most of the issues above, one other area that needs attention is how and when versions on the command line must be exact, a pattern or an implied pattern.

For geneos package install command, the version is passed to the remote web server as a string and it is the remote that determines what is returned.

For the other geneos package subcommands we can impose a glob-style pattern so that unexpected matches do not occur. These are update and uninstall. But what happens when install includes the --update flag?

What about other commands line deploy and the init commands? They should probably act like package install.