Explicit default target image list, not system

Instead of explicitly listing the future images that should be pulled
from the system image target, explicitly list the images that come from
the vendor image and pull everything else from the system image target.

As demonstrated by the addition of system_ext, a previous year's version
of Android cannot predict what logical partitions will be added in future
versions of Android. When creating a mixed build, by letting the default
image print the partitions it is providing itself, it can react
dynamically to new images being added to the super image.

Additionally, pull the misc_info.txt file from the system image target
instead of the default image target. This file will have the full list
of partitions and sizes as it comes from the later build.

Bug: 141721921
Test: Try current / previous year mixed build.
Change-Id: I78aa5a37c9d631527283cbf5498528231319943f
1 file changed
tree: 4012e3b2fee961707901e4cbf34435eb3fdb1a15
  1. common/
  2. guest/
  3. host/
  4. tests/
  5. tools/
  6. Android.bp
  7. Android.mk
  8. OWNERS
  9. TEST_MAPPING