test: pin Firefox version temporarily to 134 until artifacts tar.bz2 are available again (or a fix is provided)

[seaona]

Description

Firefox specs started failing with the error:

<failure message="Unable to obtain browser driver.
        For more information on how to install drivers see
        https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location/. Error: Error executing command for /home/circleci/project/node_modules/selenium-webdriver/bin/linux/selenium-manager with --browser,firefox,--output,json,--browser-path,/opt/firefox/firefox: Unsuccessful response (404 Not Found) for URL https://ftp.mozilla.org/pub/firefox/releases/135.0/linux-x86_64/en-US/firefox-135.0.tar.bz2
  (Ran on CircleCI Node 0 of 24, Job test-e2e-firefox)" type="Error"><![CDATA[Error: Unable to obtain browser driver.

The problem is that the artifact ending with tar.bz2 is not in present in the version 135.0, whereas it was always in previous versions, which we relied on.

https://ftp.mozilla.org/pub/firefox/releases/135.0/linux-x86_64/en-US/

From @itsyoboieltr :
It seems like firefox changed the way their releases work, so selenium cannot get the tar.

Context: https://consensys.slack.com/archives/CTQAGKY5V/p1738664570174839

Related issues

Fixes:

Manual testing steps

I re-enabled FF specs and tested this in another branch:

1. Check ci, how FF tests started running normally here

I canceled the job once I saw that the browser was successfully downloaded and specs started running

Screenshots/Recordings

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Extension Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[metamaskbot]

Builds ready [23b6ff6]

• builds: chrome, firefox
• builds (flask): chrome, firefox
• builds (MMI): chrome
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6, 7
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
  • ui: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
  • content-script: 0
  • offscreen: 0

Page Load Metrics (2040 ± 193 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	508	3000	1995	526	252
		domContentLoaded	1509	2948	1988	403	193
		load	1521	2961	2040	401	193
		domInteractive	27	194	54	37	18
		backgroundConnect	9	179	56	44	21
		firstReactRender	16	103	51	26	12
		getState	4	183	33	39	19
		initialActions	0	12	1	3	1
		loadScripts	1109	2240	1478	333	160
		setupStore	7	90	22	20	10
		uiStartup	1691	3307	2428	457	220

Bundle size diffs

• background: 0 Bytes (0.00%)
• ui: 0 Bytes (0.00%)
• common: 0 Bytes (0.00%)

[DDDDDanica]

@MetaMask/policy-reviewers There's no fundamental changes in policy, it is just for disabling e2e tests in ff as a temporary solution. Thanks for reviewing 🙏🏻

[chloeYue]

LGTM

[metamaskbot]

Builds ready [fd17af7]

• builds: chrome, firefox
• builds (flask): chrome, firefox
• builds (MMI): chrome
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5, 6, 7
  • common: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
  • ui: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
  • content-script: 0
  • offscreen: 0

Page Load Metrics (1742 ± 54 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	1473	2021	1751	121	58
		domContentLoaded	1462	2010	1715	119	57
		load	1471	2020	1742	113	54
		domInteractive	25	79	35	14	7
		backgroundConnect	11	62	33	18	9
		firstReactRender	16	104	40	27	13
		getState	5	57	15	17	8
		initialActions	0	1	0	0	0
		loadScripts	1056	1512	1250	99	48
		setupStore	8	69	19	19	9
		uiStartup	1698	2470	2002	178	85

Bundle size diffs

• background: 0 Bytes (0.00%)
• ui: 0 Bytes (0.00%)
• common: 0 Bytes (0.00%)