[e2e][couchDB] False negatives due to expected 404 console error from CouchDB on initialization

[ozyx]

Summary

When running our CouchDB e2e tests in CI, the first test ran will always fail due to detected 404 console error from CouchDB (if failOnConsoleError is enabled). We expect this to happen, because we are starting with a fresh openmct database where the mine folder has not yet been created. The initial attempt to find the mine folder results in a 404, which triggers the creation of the folder within the myItemsInterceptor.

The current solution is to disable failOnConsoleError for CouchDB tests, but this potentially masks any real (unexpected) errors that may arise. We should look into ways to mitigate the generation of this error on the e2e side, such as starting from some baseline database, or ensuring that a certain test runs first, or creating the folder in some kind of before hook.

[akhenry]

FYI, Yamcs produces tons of 404s as part of normal operations.