Allow ForeignExe to support specifying a "wildcard version" `*`

[kashev]

My use-case is similar to what @devinrsmith asked for here - For my small team, I want to be able to opt into the risks/pitfalls of allowing developer machines to run slightly different versions of external formatters like black and shfmt.

Maintainer @nedtwigg said this on this issue:

You can specify 24.2.0 yourself. I'd be okay with a PR that adds support for setting the version to *, but I want users to explicitly say "I don't care which version", because otherwise we get issues when the formatting is one way on dev machines but failing on CI because of a version difference.

Originally posted by @nedtwigg in #674

I'm opening this issue to track implementing this.

[kashev]

I'd like to help implement this, if I can. As far as I can tell, the changes required are:

• Update the conditional logic near the end of ForeignExe.confirmVersionAndGetAbsolutePath() to allow for a wildcard to be specified.
• Update any relevant tests.
• Update markdown-based documentation for both the gradle and maven plugin so that people know that this is a valid configuration, maybe with some scary language that discourages its use since it can lead to "works on my machine" problems. The files that I have on my radar for this are:
  • The maven plugin README.md
  • The gradle plugin README.md
• Update the CHANGES.md files for both plugins, as well as the top-level spotless lib one to mention this.

Am I missing anything?

[nedtwigg]

• Allow foreign executables to explicitly specify "use any found version" with '*' #2758