Simpler API for configuring simple rules

[jmfayard]

I opened a small PR to demo how we could simplify configuring the rules
#581

My vue (stolen from the Perl community) is that:

Simple things should be easy ; complex things should be possible

Rules files do the second half right, the first half not so much.

We have issues like #575 that show people would like for a way to avoid/simplify need for rules files.

I did a GitHub code search on refreshVerisons.extraArtifactVersionKeyRules see here and only 4 people have configured one during the last month.

If you look at the rules we have, some are powerful like in AndroidX but most rules are super simple and could be modeled this way:

refreshVersions {
	extraVersionRules(
		PrefixRule("koin", "io.insert-koin", "koin"),  
		PrefixRule("ktor", "io.ktor", null),
	)
}

That would not change anything fundamental for refreshVersions, the PrefixRule would simply be converted to a rules file in the background.

PrefixRule("koin", "io.insert-koin", "koin").toRawRules().shouldBe """
io.insert-koin:koin(-*)  
          ^^^^
""")

(I started to write this code already, it works)

Things to consider

• syntax for Groovy users who don't have named arguments?

[LouisCAD]

Wouldn't this be obsolete with version references support in versions catalogs?

[jmfayard]

No, not for versions.properties
Also it could be used later in the dependencies notations themselves

[jmfayard]

One thing that #211 reminded me is that once we have that,
I want to look at whether all dependencies with a common prefix share a common version,
and automatically suggest to add something like PrefixRule("ktor", "io.ktor", null),