refactor: switch to open source setupwizard lib

[proletarius101]

Since the setupwizard library was extracted from Android's source code, it would be even closer to completely FOSS if we switch the setupwizard library to it's source code rather than keep it as a blob. Another advantage is that we use the lastest upstream code (which has more eye-candy).

[oasisfeng]

Seems like it references a local module (but missing from this pull request).
Does that open source lib have a published artifect (on JCenter or else)?

[proletarius101]

It has the same layout as deagle. I think I missed the Readme part. Fixed now.
Unfortunately it's not hosted on any maven repo. Google only offer it inside the Android monorepo.

[oasisfeng]

I'm planning to remove local repo dependency (deagle) in the future, for a simpler and developer-friendly build environment.

Is there any advantage to replace AAR dependency with local repo dependency in this specific case?

[proletarius101]

My purpose is to remove blob as much as possible. That's the advantage. There's a third-party setup wizard lib (https://github.com/Trumeet/Setupwizard) on maven cloned from Google's repo. I would hold no objection if you prefer the maven one.

[proletarius101]

I recently realized that gradle supports git dependencies natively: https://blog.gradle.org/introducing-source-dependencies. Is that an acceptable option for you?