feat: support aapt optimization

[zjns]

These options help reduce the apk size when using aapt2, and --collapse-resource-names may have side effects.

[iBotPeaches]

At the moment, I don't really see a need for this. Apktool challenge is reading and understanding these sparse/collapsed applications. I don't understand a use-case where users would be disassembling and reassembling an application with intention to sparse/chunk/collapse.

I'd be interested in hearing what is leading you to this need.

[zjns]

Basically, most apps now perform the --shorten-resources-names optimization when they are compiled. It's default behavior when shrinkResouces flag enabled. When the app is large, shortening the resource path name can indeed reduce the size of the apk. As for the other two flags, there is really no need for them.

[iBotPeaches]

I'm more worried about the flag in general when used with Apktool. This optimize feature works very well at stripping things that Apktool has to piece back together. Its a challenge in of itself to just disassemble and reassemble after an optimize command.

For this to go into the core - we'd need a few tests and samples to ensure a few things

• basic build -> optimize
• optimized build -> optimize

[iBotPeaches]

At moment - going to hold on this for reasons mentioned.