This PR port most of the existing sparse Groovy DSL scripts as convention plugins, this is done to switch from decade old accumulation of scripting from the early days of Gradle to best practice of today. Fortunately our script were well split.

For the full motivation see #3446

At this stage, this PR port is almost a 1 to 1, i.e. it doesn't aim at introducing or changing the build behavior. It is not complete, the coverage, shipkit, spotless, licenses still remain to be converted.

tl;dr: what this PR does is changing apply from: ....gradle to a convention plugin plugins { id("mockito....-conventions") }. THese plugin are added in the standard buildSrc

• Create the buildSrc project for the conventions plugins

  • Declares the moved plugin in the version catalog file

• Java lib config

  • java-library.gradle --> mockito.library-conventions.gradle.kts, which applies other convention plugins below

  • java-library.gradle --> mockito.java-library-conventions.gradle.kts, also sets up Java related configurations found in the root build.gradle, and applies mockito.java-conventions

  • osgi.gradle --> mockito.osgi-conventions.gradle.kts, this only applies the plugin as config differ between mockito-core and mockito-junit-jupiter.

  • java-publication.gradle --> mockito.publication-conventions.gradle.kts

  • checkstyle.gradle --> mockito.checkstyle-conventions.gradle.kts

  • errorprone.gradle merged in mockito.java-library-conventions.gradle.kts

  • animalSniffer config in mockito-core/build.gradle and mockito-junit-jupiter/build.gradle --> extracted to mockito.java-backward-compatibility-checks-conventions.gradle.kts

• Tests

  • java-test.gradle --> mockito.test-conventions.gradle.kts (which applies mockito.test-jfr-profiler-conventions, mockito.java-conventions)
  • jfr.gradle --> mockito.test-jfr-profiler-conventions.gradle.kts
  • test-launcher.gradle --> mockito.test-launcher-conventions.gradle.kts
  • retry-test.gradle --> mockito.test-retry-conventions.gradle.kts

• Javadoc

  • mockito-core/javadoc.gradle and mockito-junit-jupiter/javadoc.gradle --> mockito.javadoc-conventions.gradle.kts
  • mockito-core/src/main/javadoc -> config/javadoc/resources, because it's shared with junit jupiter extension.

Now Mockito Libraries (core and extensions) declare this

plugins {
    id("mockito.library-conventions")
    id("mockito.java-backward-compatibility-checks-conventions") // if needed
    id("mockito.javadoc-conventions") // if needed
}

And integration tests have this

plugins {
    id("java")
    id("mockito.test-conventions")
}

Android test project also applies our convention.

plugins {
    id("com.android.application")
    id("kotlin-android")
    id("mockito.test-conventions")
}

Two approaches for the review

1. Take a look at all the file changes.
2. Review commit by commit, starting with this one : 94132ac, navigate back and forth with previous / next.

Checklist

• Read the contributing guide
• PR should be motivated, i.e. what does it fix, why, and if relevant how
• If possible / relevant include an example in the description, that could help all readers
  including project members to get a better picture of the change
• Avoid other runtime dependencies
• Meaningful commit history ; intention is important please rebase your commit history so that each
  commit is meaningful and help the people that will explore a change in 2 years
• The pull request follows coding style
• Mention Fixes #<issue number> in the description if relevant
• At least one commit should mention Fixes #<issue number> if relevant