Fix/unknown Android classes

[aSemy]

Hopefully will improve #71

• Set up Android integration test
• Try triggering Android artifact transformations (as discovered in AndroidX classes produce Error class: unknown class in generated HTML #71 (comment))
• tidy up code in Android/Kotlin adapters
• improve setting up of Dokka test projects (so local.properties is generated properly)
• Fix Failed to install the following Android SDK packages as some licences have not been accepted. error on GitHub action

Significant changes

• DokkaSourceSetIdSpec.sourceSetName mutability has been deprecated. Instances of this class is used in Sets, and so its hashcode/equals must remain constant.
• Minimum Android version updated to 4.2.2

[aSemy]

hey @EdricChan03 👋 Are you able to check out this branch, publish to to Maven Local, and give it a go in your project? I think it should fix your issue.

(the tests are failing because of a inconsequential difference in the generated HTML)

[EdricChan03]

It seems that the index.html isn't correctly generated? (Or rather, it appears to be in the wrong directory) It fails with the following exception:

Execution failed for task ':dokkatooGeneratePublicationHtml'.
> A failure occurred while executing dev.adamko.dokkatoo.workers.DokkaGeneratorWorker
   > /<...>/androidx-ktx-extras/build/dokkatoo/html/androidx/browser/browser-ktx/index.html

This is what the build directory structure looks like for that particular module:

Not sure if it's something to do with this config:

dokkatoo {
    // TODO: Remove
    dokkatooPublicationDirectory.set(layout.buildDirectory.dir("dokkatoo"))
    dokkatooConfigurationsDirectory.set(layout.buildDirectory.dir("dokkatoo-config"))
}

I don't see any <ERROR class> thingy in the HTML output though, so I guess that's a partial success 🥳

EDIT: Build Scan for index.html issue

[aSemy]

Thanks a lot for checking! It's a good sign.

I'm not sure what the problem might be with the index.html file. Possibly it's a bug from another change I've made since v1.3.0.

I'll finish up the work in this PR and if there's another bug to fix, then we can make a new issue for it.