ISSUE-137: Redefine plugin artifact to work with gradle plugin DSL

[DanielJette]

What does this change accomplish?

Resolves #137

How have you achieved it?

After much experimentation, the solution to properly publish the plugin seems to have been to rename the artifact to dev.testify.gradle.plugin (previously just plugin). This allows the plugin to conform to the Plugin DSL .

Scope of Impact and Testing instructions

1. Check out this branch (137-gradle-plugin)
2. Publish the Gradle Plugin to the local Maven repository (./gradlew Plugin:publishToMavenLocal)
3. Create a new Android app project in Android Studio
4. Edit the settings.gradle.kts to reference mavenLocal()
5. Edit the root build.gradle.kts:

   plugins {
       id("dev.testify") version "2.0.0" apply false
   }

6. Edit the app build.gradle.kts:

   plugins {
       id("dev.testify")
   }

7. Gradle sync and verify that it configures correctly
8. Open the ExampleInstrumentedTest and add a new test:

   @get:Rule val rule = ScreenshotRule(MainActivity::class.java)
   
   @ScreenshotInstrumentation
   @Test
   fun default() {
       rule.assertSame()
   }

9. Verify ./gradlew app:screenshotRecord
10. Verify ./gradlew app:screenshotTest

Alternatively, I have also published this as a preview build. You can test this out by setting the version to 3.0.0-preview04

Notice

Warning

This change must keep main in a shippable state; it may be shipped without further notice.

[AndroidTestifyBot]

✅ Success! - Legacy Sample screenshot test results

View build for commit b260dbb

[AndroidTestifyBot]

✅ Success! - Flix Sample screenshot test results

View build for commit b260dbb

[AndroidTestifyBot]

✅ Success! - Flix Library screenshot test results

View build for commit b260dbb

[DanielJette]

@jaredh This seems to work fine without the java-gradle-plugin