Collect Selenium results for beta browsers

[Elchi3]

I've been manually collecting results on beta browsers but ideally we want to collect results automatically. I think this PR should do that.
This will help to reduce manual BCD PRs that people usually submit during the beta phase of browsers. See also https://github.com/mdn/community-meetings/blob/main/23-12-11/minutes.md#bcd where Ruth asked about this.

[Elchi3]

In Beta browsers there are sometimes A/B tests which can skew the test results.

For Chrome, I found https://chromium.googlesource.com/chromium-variations/ and so open -a Google\ Chrome\ Beta --args --fake-variations-channel=stable should hopefully disable the variation and make Beta act like a stable browser release. Is it somehow possible to tell Selenium to launch Chrome beta with --fake-variations-channel=stable?
(mdn/browser-compat-data#23207 (comment))

For Firefox, something similar exists, but I haven't done the research yet how to prevent it from happening there.

[queengooborg]

filterVersions is also used in the find-missing-reports script, which notifies us if there is any critical report files missing. We should add a new argument that allows us to specify if we want to include beta releases.

One of my other concerns is that we have no way of tracking if a report came from a beta or stable version of the browser, which could potentially skew our results when running the update-bcd script. It would also make it harder to know if we need to re-run the collector on the stable version of the browser and obtain support results from a stable release. If we could update the filename saved by the Selenium script to clarify it's for a beta release, that would be helpful.