perf: convert chmod calls to mode arguments

[paul-soporan]

What's the problem this PR addresses?

We use a lot of chmod calls where writeFile (/changeFile) or mkdir with a mode argument could be used.

From my testing, a single writeFileSync(..., {mode}) call is 21.05% faster than 2 calls (a writeFileSync(...) and a chmodSync(...)):

• 1 call - 0.15ms:

fs.writeFileSync(`a`, {mode: 0o777});

• 2 calls - 0.19ms:

fs.writeFileSync(`a`, ``);
fs.chmodSync(`a`, 0o777);

How did you fix it?

Used the mode argument wherever possible.

Checklist

• I have read the Contributing Guide.

• I have set the packages that need to be released for my changes to be effective.

• I will check that all automated PR checks pass before the PR gets reviewed.

[merceyz]

I looked into this a while ago but noticed ZipFS didn't implement it so I left it for another time, seems that time has come

berry/packages/yarnpkg-fslib/sources/ZipFS.ts

Lines 1119 to 1132 in 857e21f

	writeFileSync(p: FSPath<PortablePath>, content: string | Buffer | ArrayBuffer | DataView, opts?: WriteFileOptions) {
	const {encoding, index, resolvedP} = this.prepareWriteFile(p, opts);
	if (index !== undefined && typeof opts === `object` && opts.flag && opts.flag.includes(`a`))
	content = Buffer.concat([this.getFileSource(index), Buffer.from(content as any)]);
	if (encoding !== null)
	content = content.toString(encoding);
	const newIndex = this.setFileSource(resolvedP, content);
	if (newIndex !== index) {
	this.registerEntry(resolvedP, newIndex);
	}
	}