chore: upgrade chromedriver to 138

[DanielSinclair]

Fixes BX-####
Figma link (if any):

What changed (plus any additional context for devs)

Screen recordings / screenshots

What to test

---

PR-Codex overview

This PR focuses on updating dependencies related to Chrome and Selenium, specifically upgrading versions and adjusting import statements in the codebase.

Detailed summary

• Updated chrome version from 133 to 138 in .github/actions/chromeTestsSetup/action.yml.
• Changed import statements for chrome and firefox in e2e/helpers.ts to use * as.
• Adjusted setChromeOptions to cast options as chrome.Options.
• Updated @types/selenium-webdriver from 4.1.15 to 4.1.28 in package.json.
• Updated chromedriver version from 133 to 138 in package.json.
• Updated selenium-webdriver version from 4.24.1 to 4.34.0 in package.json.
• Updated @bazel/runfiles version from 5.8.1 to 6.3.1 in yarn.lock.
• Updated checksum for @bazel/runfiles in yarn.lock.
• Updated checksums for @types/selenium-webdriver, chromedriver, and selenium-webdriver in yarn.lock.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​bazel/​runfiles@​5.8.1 ⏵ 6.3.1			+1
	@​types/​selenium-webdriver@​4.1.15 ⏵ 4.1.28
	chromedriver@​133.0.3 ⏵ 138.0.3	+2			+1
	selenium-webdriver@​4.24.1 ⏵ 4.34.0	+1		+1	+1

View full report