Add node 22, chrome 134, and ff138 images for base-internal and browsers-internal

[cacieprins]

This is in preparation for Electron 35.

[MikeMcC399]

Please don't make these case changes in your internal PR.

The case is only used internally.

All the visible names are correct.

[cacieprins]

Prettier did this automatically - I'll revert

[MikeMcC399]

@cacieprins

Let me check for Prettier separately! Thanks for explaining where it came from and for reverting.

[MikeMcC399]

Suggested change

	},
	}

I missed removing the comma

[MikeMcC399]

Thanks for the changes!

[MikeMcC399]

@cacieprins

I don't know what happened with Prettier. It's not asking for any format changes when I run it here.

$ npm ci

added 179 packages, and audited 180 packages in 3s

51 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
$ git switch node-22.14
$ npm run format:check

> [email protected] format:check
> prettier --check .

Checking formatting...
All matched files use Prettier code style!

CircleCI is happy as well:

https://app.circleci.com/pipelines/github/cypress-io/cypress-docker-images/2548/workflows/039ba3b7-0340-4082-87ab-aff2f29e4a97/jobs/78751

[MikeMcC399]

@cacieprins

For Corepack you can set COREPACK_ENABLE_AUTO_PIN=0 to stop it adding a packageManager field on its own.

I also added an enhancement request to ask Corepack NOT to change the package manager on its own, like here from npm to Yarn.

There are several other related enhancement requests for Corepack to change some of this and make it more user-friendly, however it looks like nobody is working on Corepack anymore since the Node.js TSC decided to stop distributing Corepack with Node.js 25 and above, so I don't know if it will ever get looked at.

[MikeMcC399]

@cacieprins

It looks like you must have had an old 2.x version of Prettier globally installed when you ran Prettier.

If you run npm ci before using npm run format then you should get the intended results using "prettier": "3.5.3".

There was a bug in Prettier 2.x where Markdown links were incorrectly changed to lowercase.

---

One of the Corepack maintainers has changed the auto-pin to be non-default. Hopefully that will get released soon and prevent accidental changes to package.json files!