[LinuxBionic] Disable RemoteExecutor during test runs

[steveisok]

Fixes #76140

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[steveisok]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jkotas]

Is there a reason why Linux Bionic does not support remote executor? I would expect that remote executor should work on Linux Bionic just fine. Linux Bionic is basically plain vanilla Linux. It does not come with the same limitations as Android apps.

[jkotas]

Also, we have a ton of RemoteExecutor tests and they seem to be all running on Linux Bionic today. Why are we seeing the failure on just 3 tests? It suggests that the problem is specific to the 3 tests that are failing.

[akoeplinger]

I agree with Jan, if possible we should just disable the failing tests

[directhex]

We’re restricted to using Google Android images in CI, because our internal partner hasn’t provided images of anything closer to their final production environment to run on. So technically we don’t have issues doing things on Bionic in general, in practice there are certain constraints in our CI environment which are beyond our team’s ability to work around (e.g. Google’s SELinux configuration blocks creation of domain sockets in /data/local/tmp, which is the only directory we can write our tests to without trying to invoke the whole APK infrastructure, whose functionality on the target devices isn’t clear)