Verify that Android-specific task data is ingested by the `testselect` model

[ncalexan]

There's a belief -- perhaps unjustified -- in the Firefox for Android engineering team that mach try auto "does not work" for Android development. Certainly mach try auto pushes like this one, which modified many build.gradle files, don't kick off Android-specific jobs like build-components or test-components or Fenix-specific UI test jobs. (It did kick off a gvjunit job.)

This ticket tracks verifying that the new, fairly non-standard, Android tasks are being ingested by the appropriate models, so that Firefox for Android engineers can use mach try auto fearlessly. Hopefully, exclusively!