Add piping and bringup nodes for _vulkan and _opengles suites. (#162020)

Towards https://github.com/flutter/flutter/issues/161333.

This adds the initial `.ci.yaml` configuration (marked `bringup: true`),
without changing the existing shard to avoid the problems we ran into
last time when I renamed the shard atomically, as well as piping for
providing context in which the test will run (Vulkan or OpenGLES), which
can't be introspected in the _running_ app.

In a follow-up PR I'll:

- Edit `AndroidManifest.xml` before the suite, setting `ImpellerBackend`
appropriately
- Move the bringup nodes to presubmit
- Delete the existing (legacy) node

TESTOWNERS

@@ -323,12 +323,14 @@
 # https://github.com/flutter/flutter/issues/82068
 #
 # analyze @Piinks @flutter/framework
+# android_engine_vulkan_tests @matanlurey @jonahwilliams
+# android_engine_opengles_tests @matanlurey @jonahwilliams
 # build_tests @andrewkolos @flutter/tool
 # ci_yaml flutter roller @keyonghan @flutter/infra
 # coverage @goderbauer @flutter/infra
 # customer_testing @Piinks @flutter/framework
 # docs @Piinks @flutter/framework
-# flutter_driver_android_test @matanlurey @johnmccutchan
+# flutter_driver_android_test @matanlurey @jonahwilliams
 # flutter_packaging @christopherfujino @flutter/infra
 # flutter_plugins @stuartmorgan @flutter/plugin
 # framework_tests @Piinks @flutter/framework