Detect mill plugins, that require an incompatible Mill version

[lefou]

This is a successor to #466.

Some plugins in the Mill ecosystem tend to depend on the latest Mill version and might no longer be compatible to lower versions.

Example: plugin mill-foo depends on Mill 0.11.9 and (accidentally) uses a new API. A projects still on Mill 0.11.8 that bumps it's dependency on mill-foo suddenly errors but there is no clear indicator of the cause, just some arbitrary exception about some missing class or so.

Technically, coursier should be able to inspect the provided-scoped dependencies of mill-foo and match it against a version range of [0.11.0,0.11.8], which represents all supported Mill APIs. If there is no match, it should fail with a actionable or at least reasonable error message.

See also:

• Add some kind of API to require a minimum version of mill #466
• Add option to resolve transitive provided deps coursier/coursier#2891 (comment)
• https://get-coursier.io/docs/other-version-handling#reconciliation