fix(e2e): use chrome stable instead of canary for web tests COMPASS-10009 COMPASS-10010 COMPASS-10012

[gribnoysup]

The e2e tests for compass web on chrome right now are extremely flaky, most of them are randomly failing with "tab crashed". While there's a small chance that it's actually somehow caused by us, I think the chances are higher is that it's related to us using chrome canary for testing. I think it's really not required for us to run tests on canary, so to see if that's the root cause and to potentially resolve the flakes, I'm changing the logic a bit to use stable chrome when testing web (for FF we only can use latest unfortunately)

[addaleax]

Is this meant to be temporary? In general, getting early warnings about changing browser behavior isn't a bad thing

[gribnoysup]

I wasn't planning to revert this, but I'm open to opinions. I don't think compass-web does anything that really requires us to test against the very latest (potentially really buggy) versions of browsers and the latest stable is probably ahead enough compared to what most of compass users would actually be using. I generally agree with you, but I think specifically canary is way too risky to have as a default for the bulk of the browser e2e tests. We can try either setting this to beta for chrome or to have a separate, non-blocking set of tests running against canary, what do you think?

[gribnoysup]

(I'll merge to leave the CI greener for the weekend, but really open to revisiting this later)