Open
Description
The problem
We currently run MV2 AND MV3 test on chrome and only MV2 tests on firefox. Once we ship MV3 to main no new builds of the extension will need to run the MV2 tests because we will only be shipping the MV3 code. We do have to maintain both codepaths (the MV3 feature flag) because we are not ready for Firefox MV3 yet. We have relied upon a few chrome specific APIs to get to MV3 launch readiness (offscreen document, whereas we may need to explore event pages in firefox).
Running both MV2 and MV3 tests for chrome will be wasteful to our CI billed time.
The solution
Once we ship MV3 and chrome has stopped accepted MV2 builds we can safely deprecate MV2 E2E tests on chrome. This doesn't save us much except that we can eliminate one step of the CI process