Add configuration options that make working with AAB apps easier.

[reidbaker]

Android traditionally used apk's as the deployment binary format as time has moved forward Google play and Android have migrated to using AAB files which are all the files that might been needed for any device then the play store bundles those up into an apks file for a specific device.

As android introduces new features (like device targeting) some of those features rely on having an aab bundled app. Flutter has the ability to build aab files with flutter build aab but when we authored that commend the goal was to build the bundle for Google Play and not as part of the dev workflow.

The android team did a deep investigation on what it would take to migrate all flutter build command to build an aab then an apk[s] from that aab and discovered we would need to break multiple existing flags/user-flows. See flutter/flutter#166751.

This bug tracks investigating what flutter can do to make day in and day out development easier for developers that need or want to use aab files.

Goal: Make any set of configuration options that allow aab build apps launch on a device with a debugger attached.
Ideas:

• Add a way to set a device configuration file
• Automatically run bundle tool for the preset configuration files
• Automatically run bundle tool for the attached devices
• Make it possible and/or document how to use the debugger in android studio with an app launched from the command line.

[reidbaker]

@abdallahshaban557 @jwren FYI