Added new fork of leafdigital Kanji draw application

• The app complies with the inclusion criteria
• The original app author has been notified (and supports the inclusion)
• All related fdroiddata and RFP issues have been referenced in this merge request
• The upstream app source code repo contains the app metadata (summary/description/images/changelog/etc) in a Fastlane or Triple-T folder structure
• Builds with fdroid build
• Releases are tagged

---

This is !6073 (closed) with a dedicated App ID.

Kanji draw was previously included in F-Droid, but has since been removed due to a weak build signature. The upstream project also seems to be dead, the last commit was 9 years ago and the author has not responded to requests. This new app is a fork of the original application, maintained by myself.

Several other modifications were applied to the project:

• Outstanding pull requests were merged (updated KanjiVG database, Brazilian Portuguese translation)
• Gradle build scripts were added (created with Android Studio)
• The repository was restructured to be in line with current Java standards
• The separate main and android branches were merged
• A data collection anti-feature was disabled by default, but left intact so it can still be enabled by users
• The readme was improved and build instructions were added

I'm not sure about the metadata: Is this a common standard now? Should I add Fastlane/Triple-T metadata files?