Bump Kotlin to 1.7.10

[utzcoz]

The AGP 7.3.0 only supports kotlin-android 1.5.20 and higher version.

[utzcoz]

@brettchabot Looks like current Kotlin configuration can't use Kotlin 7.10 directly. I will investigate it at weekend to see why.

[utzcoz]

@brettchabot I didn't find the root cause of building error after bumping Kotlin to 1.7.10, but I found that the utils module's Kotlin plugin dependency has affected its usage by other modules, like shadowapi module when bumping Kotlin to latest version. I think I can understand a little of what @kingargyle said about Kotlin's compatibility. cc @hellosagar @hoisie .

[utzcoz]

The stacktrace is here:

* What went wrong:
Could not determine the dependencies of task ':errorprone:test'.
> Could not resolve all task dependencies for configuration ':errorprone:testRuntimeClasspath'.
   > Could not resolve project :utils.
     Required by:
         project :errorprone > project :shadowapi
      > The consumer was configured to find a runtime of a library compatible with Java 8, packaged as a jar, preferably optimized for standard JVMs, and its dependencies declared externally, as well as attribute 'artifactType' with value 'jar'. However we cannot choose between the following variants of project :utils:
          - kotlinCompilerClasspath
          - kotlinKlibCommonizerClasspath
        All of them match the consumer attributes:
          - Variant 'kotlinCompilerClasspath' capability org.robolectric:utils:4.9-SNAPSHOT declares a component, as well as attribute 'artifactType' with value 'jar':
              - Unmatched attributes:
                  - Doesn't say anything about its component category (required a library)
                  - Doesn't say anything about how its dependencies are found (required its dependencies declared externally)
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
                  - Doesn't say anything about its target Java version (required compatibility with Java 8)
                  - Doesn't say anything about its elements (required them packaged as a jar)
                  - Doesn't say anything about its usage (required a runtime)
          - Variant 'kotlinKlibCommonizerClasspath' capability org.robolectric:utils:4.9-SNAPSHOT declares a component, as well as attribute 'artifactType' with value 'jar':
              - Unmatched attributes:
                  - Doesn't say anything about its component category (required a library)
                  - Doesn't say anything about how its dependencies are found (required its dependencies declared externally)
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
                  - Doesn't say anything about its target Java version (required compatibility with Java 8)
                  - Doesn't say anything about its elements (required them packaged as a jar)
                  - Doesn't say anything about its usage (required a runtime)
        The following variants were also considered but didn't match the requested attributes:
          - Variant 'apiElements' capability org.robolectric:utils:4.9-SNAPSHOT declares a library compatible with Java 8, packaged as a jar, preferably optimized for standard JVMs, and its dependencies declared externally:
              - Incompatible because this component declares an API of a component and the consumer needed a runtime of a component
              - Other compatible attribute:
                  - Doesn't say anything about artifactType (required 'jar')
          - Variant 'mainSourceElements' capability org.robolectric:utils:4.9-SNAPSHOT declares a component, and its dependencies declared externally:
              - Incompatible because this component declares a component of category 'verification' and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about artifactType (required 'jar')
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
                  - Doesn't say anything about its target Java version (required compatibility with Java 8)
                  - Doesn't say anything about its elements (required them packaged as a jar)
                  - Doesn't say anything about its usage (required a runtime)
          - Variant 'testResultsElementsForTest' capability org.robolectric:utils:4.9-SNAPSHOT:
              - Incompatible because this component declares a component of category 'verification' and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about artifactType (required 'jar')
                  - Doesn't say anything about how its dependencies are found (required its dependencies declared externally)
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
                  - Doesn't say anything about its target Java version (required compatibility with Java 8)
                  - Doesn't say anything about its elements (required them packaged as a jar)
                  - Doesn't say anything about its usage (required a runtime)

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.4.2/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 1s
2 actionable tasks: 2 up-to-date

[utzcoz]

@brettchabot From your work to using latest AndroidX test libraries at #7683, I think we also need to add @aar or @jar to utils module to bypass resolving problem. I will give a try.

[utzcoz]

@brettchabot @hoisie I think we can bump Kotlin to 1.7.10 now after some weekend's work. There are some changes that need to highlight:

1. Remove gradle module metadata for utils module to avoid potential compatibility problems after released. When Robolectric other modules use utils module, we have encountered compatibility problems of variant resolving. Before we introduce Kotlin code for release code, IMO it's safe to remove gradle module metadata from Robolectric's modules that use Kotlin for testing code.
2. Using java/main to replace kotlin/main for utils module to avoid d8 error when analyzing empty kotlin/main directory. Although utils module doesn't have code in kotlin main source set, but Kotlin plugin adds it to utils module variant's artifacts that are recognized by d8 tasks.

[utzcoz]

Friendly ping @hoisie @brettchabot for review.