Use convention plugins instead of shared subproject block

[tweksteen]

The current setup to share the logic/dependencies between projects is to use a subproject {} block in the root project's build.gradle. This is not the best practice, as this creates an overlap of configurations that are specific to only some subprojects (for instance, the Android dependencies are only applied to Android subproject). Here are a couple of symptoms of the issue:

• Mark kotlin target JVM as 1.8 #1262 while we restrict the target JVM to 1.8 for most subprojects, this is not the case for the api-doclet. But the default configuration forces it to use 1.8.
• Reference to unknown subprojects are not caught (e.g. conscrypt-benchmark-caliper doesn't exist).

The official documentation recommends defining a convention plugin to share common traits between the build files.

From my reading of the root build.gradle. I think there are at least 2 conventions that we could define: built for Android or built for OpenJDK (see the current boolean androidProject).

[tweksteen]

Mostly fixed in PR #1386! Thanks @prbprbprb