Switch usages of legacy-test to android.test.base

The legacy-test library has been deprecated in favour of the
android.test.base library which will be exposed to developers in
similar manner to android.test.runner and android.test.mock.

Bug: 30188076
Test: make checkbuild && make droid && flash
Change-Id: I36a9ccf8a1b4b7b75ce1ca4893daa3db6e660b30

core/tasks/check_boot_jars/package_whitelist.txt

@@ -121,7 +121,7 @@ com\.android\..*
 
 
 ###################################################
-# legacy-test.jar
+# android.test.base.jar
 junit\.extensions
 junit\.framework
 android\.test

target/product/core_minimal.mk

@@ -109,7 +109,7 @@ endif
 # The order of PRODUCT_BOOT_JARS matters.
 PRODUCT_BOOT_JARS := \
     $(TARGET_CORE_JARS) \
-    legacy-test \
+    android.test.base \
     ext \
     framework \
     telephony-common \

target/product/core_tiny.mk

@@ -94,7 +94,7 @@ endif
 # The order matters
 PRODUCT_BOOT_JARS := \
     $(TARGET_CORE_JARS) \
-    legacy-test \
+    android.test.base \
     ext \
     framework \
     telephony-common \

target/product/runtime_libart.mk

@@ -27,7 +27,7 @@ PRODUCT_PACKAGES += \
 
 # Additional mixins to the boot classpath.
 PRODUCT_PACKAGES += \
-    legacy-test \
+    android.test.base \
 
 # Why are we pulling in ext, which is frameworks/base, depending on tagsoup and nist-sip?
 PRODUCT_PACKAGES += \