Disable EG tests after SbTime API deprecation

[hlwarriner]

These tests are no longer blocking but the failures can still be confusing for Cobalt developers.

b/302733082

Change-Id: I4d546e71ffa13fff4d6fe7f9903dd492de0bedb2

[andrewsavage1]

@gbournou I think you were saying that these tests just need to be regenerated?

My only worry with disabling them completely would be that real breakages would go unnoticed and make it harder to integrate the new version of evergreen tests that you're working on, but if that's not a concern for y'all then I don't have an issue with this

[hlwarriner]

@gbournou I think you were saying that these tests just need to be regenerated?

My only worry with disabling them completely would be that real breakages would go unnoticed and make it harder to integrate the new version of evergreen tests that you're working on, but if that's not a concern for y'all then I don't have an issue with this

Oh yeah I'm planning to just disable them for a day (or a few...whenever the trunk nightly release succeeds and puts the new binaries up on Omama/Lorry). Sorry, I mentioned that in the todo comment but not in the PR description.

We used to have to temporarily disable the tests when Starboard APIs were changed to unblock the nightly release that puts the new packages up on Omaha/Lorry. We don't need to anymore, since these checks are non-blocking, but we already had a question about the failures in the Cobalt team chat - so just wanted to avoid more confusion.

go/sustainable-eg-tests will fix this but isn't ready yet.