Temporarily disable Editor UI tests

[oguzkocer]

We are temporarily disabling the Editor UI tests to give us some time to address the aztec/gutenberg issue mentioned here.

To test:

• CI should pass.

PR submission checklist:

• I have considered adding unit tests where possible.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[peril-wordpress-mobile]

You can test the changes on this Pull Request by downloading the APK here.

[oguzkocer]

@jkmassel @rachelmcr I am fairly sure that this PR will fix the CI issue we are having, but unfortunately it's hard to make sure that's the case because when I run the tests locally the missing mock errors show up even though these never do in the CI.

I think we'll need to carve out some time to work on these UI tests and fix them once and for all. For now, I think this is safe enough of a PR to just merge. 🤷‍♂

[rachelmcr]

This look good to me. All tests under .org.wordpress.android.e2e are now disabled.

when I run the tests locally the missing mock errors show up even though these never do in the CI.

There are some mocks errors that I see when I run wPScreenshotTest, but we exclude that test from the connected test run on CI since it's only used to generate screenshots for the app store — so that won't affect our CI test runs. (It would be nice to clean that up at some point, though.) All other connected tests pass for me locally.