Add Auto-Manifest plugin

[tasomaniac]

Fixes #248

Auto-Manifest automatically generates AndroidManifest packageName based on Gradle module structure. Since Splitties has modules and fun-packs separated, it would put modules in the middle of the package. That's why the plugin is applied under modules/build.gradle.kts. This made me realize a small issue on the plugin and released a fix.

One change required in the code (Preview.kt and UiPreview.kt) was that views-dsl used views.dsl.core as packageName and I had to change the imports. Since these imports are not exposed, I don't think it is a breaking change.

[tasomaniac]

It is nice that we have some unnecessary code removal. 84 lines added (unfortunately because I needed to add project param to all gradle files)

[LouisCAD]

Can you retarget to the develop branch please?

[LouisCAD]

Thanks for your PR!
There's a few possible improvements. If you want and have the time, please address them. Otherwise, please tell me and I'll do that myself before merging, no problem.

[LouisCAD]

@tasomaniac I think you've seen that the latest build fails (here's the error in the Gradle scan: https://scans.gradle.com/s/vswhzdzwuz6wa/console-log?task=:modules:views-dsl:compileDebugKotlinAndroid)

It looks like the manifest of the views-dsl module is not taken into account.
Is it because auto-manifest assumes the default path for the manifest? Or maybe because something runs too late or too early relative to another thing dealing with the manifest path?

[tasomaniac]

Hmmm, there are other modules where their manifest is present in the same place. There is nothing special about that module. I will check soon.