Add arm64 to example supported cpu values

[MasterOdin]

What's the problem this PR addresses?

PR adds arm64 to the list of example architectures for the CPU for the .yarnrc config file. I added this given that it's probably one of the most popular things people might add to this field given the existence of the Apple M1/M2 machines, and that I originally stumbled onto this field about just that, and the clickthrough to the node docs was unnecessary if the docs just listed this field. There is precedent in having the arm64 field listed in the example per the manifest.json file:

berry/packages/docusaurus/static/configuration/manifest.json

Lines 69 to 77 in 2634e6c

	"cpu": {
	"title": "Set of CPU architectures on which this package works.",
	"description": "The value of `process.arch()` will be compared at install-time against this set. Should no matches be found, any postinstall script the package define will be skipped. If the package was exclusively depended upon via `optionalDependencies` entries, the package won't be installed at all.",
	"type": "array",
	"items": {
	"type": "string"
	},
	"exampleItems": ["x64", "ia32", "arm64"]
	},

How did you fix it?

By adding arm64 to the list of supported CPU architectures.

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.

[arcanis]

Looks reasonable, thanks!