feat: begin work on adding Ktlint / Android build step to the repo

[TheRogue76]

This PR aims to add Ktlint to the repo and maybe setup some extra build steps for Android like we have in iOS. This is an effort to make sure stuff like #1150 can never happen again.

[TheRogue76]

Let's see if https://github.com/lottie-react-native/lottie-react-native/actions/runs/7427881570/job/20214305445 fails. If it does, i'll add it to the base build steps in CI and remove the trigger so it runs on every PR

[TheRogue76]

It doesn't. gradle assemble straight up ignores it, it's only gradle build that calls lottie-react-native:lint. The linter is ours and already existed as one of our verification gradle tasks, it wasn't a third party linter. @matinzd

I can rename our build:android jobs to assemble:android (because that is what they are actually doing) and add a new job to actually build android, or run ./gradlew lottie-react-native:lint if we want it to be faster and combine the ktlinter job and that job together, but it needs to be done in the apps, because if we run it in core, it is gonna error out due to not seeing dependencies like react native and others

[TheRogue76]

Scrapping the PR, will do another one, with the linter gradle command only