[ci] Improvements for emulator test jobs

[pjcollins]

The setup execution time for non-device tests has been improved by
moving a handful of adb commands from BaseTest to DeviceTest setup.
These would run for nearly every test run and result in a lot of waiting
due to some RunProcess failures and timeouts.

The output from the shell command we run to check if a device is online
is now cached and only refreshed when required by certain tests/asserts.

The AssertHasDevices check has been consolidated into DeviceTest
setup, and removed from individual tests in most cases.

Attempts to restart the emulator if a test determines that it is
inaccessible have been fixed, and emulator data will not be reset in
this case.

I played around with a handful of emulator launch settings and found
that removing the no-boot-anim and headless UI options improved the
reliability of nightly LocalizationTests, and resulted in faster boot
times locally. These options are now disabled for those tests.

The DeploymentTest class has been replaced by TimeZoneInfoTests and
LocalizationTests, and the other tests in that class have been moved
to InstallAndRunTests. TimeZoneInfoTests and LocalizationTests
will now validate command line output rather than trying to press a
button and read a UI element. This should make them more reliable and
faster.

The TimeZoneInfoTests and LocalizationTests suites have been moved
into separate test stages in the nightly test job.

All nightly tests now run against our .NET build/test artifacts rather
than classic XA.

An issue that caused LocalizationTests nodes 11 and 12 to not contain
any tests has been fixed.

An issue that caused LocalizationTests node 1 to also run tests from
node 11 and node 12 has been fixed.

Test result attachments have been fixed for TimeZoneInfoTests and
LocalizationTests, ensuring that we capture the right logcat and build
files for each test variant.

An issue causing binlog files to be overwritten by tests that use
multiple build targets has been fixed by naming the binlog file after
the build log file.

Console output verbosity has been set to normal for dotnet test
invocations, which should help with debugging.

Test NUnit packages have been updated to their latest versions.

[pjcollins]

Testing this with https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=7228766&view=results.

[pjcollins]

Latest nightly test run: https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=7374786&view=results

[pjcollins]

I think this is getting pretty close so opening it up for some review. There are still reliability issues, but I think this is move in the right direction.

After moving all of the nightly tests to run against our .NET artifacts I've been seeing some SSL related issues on API 23 and below which may be real issues:
https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=7369649&view=ms.vss-test-web.build-test-results-tab&runId=69041435&resultId=100139&paneView=debug

[jonathanpeppers]

Some of these if I run them locally and forgot to attach a device, it would give a nice error message. Was there a reason to remove it?

[pjcollins]

I moved this check into DeviceTest setup so we don't need to define it on every test. We will also attempt to acquire an android target during setup now as well if one is not available.

[dellis1972]

This is all good stuff.

It might be nice however to keep at least one test which checks a Button Click? (If we removed them all). Since this helps to confirm that our Events works and possiblly that the CodeBehind stuff works.

[pjcollins]

It might be nice however to keep at least one test which checks a Button Click? (If we removed them all). Since this helps to confirm that our Events works and possiblly that the CodeBehind stuff works.

The DeploymentTests class that I replaced had two other tests that click a button, I've moved those into InstallAndRunTests. These will hopefully continue to provide this coverage, and we can add more here in the future as needed.

[pjcollins]

Previous nightly was close to green with a re-run: https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=7396250&view=results.

Queueing one more against this branch to see how it fairs:
https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=7411683&view=results

I think this is now in a place where it can be merged and we can continue to iterate on improvements.

[jpobst]

🤞 for more stable tests!

In future PRs, we can look at dotnet-test-slicer and start-stop-emulator.yaml as possible improvements.