One main job that androiddeployqt currently does is dependency scanning, which we could include under it:

• Module libraries
• Jar files
• Permissions and features
• Plugin libraries

Then writing all this into the libs.xml file as an Android project's resources.

Since CMake, has already all those details readily available, we should also cut the extra step of using androiddeployqt. We would still have some steps where qmlimportscanner is called externally, and that's something that CMake can also handle.

It's a good idea here to add some tests to ensure the same resulting artifacts compared to androiddeployqt.