docs: Update getting-started.md

[blueberryapple]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[ x ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

Updated getting started command to include instructions for yarn 2+.

Is there anything you'd like reviewers to focus on?

[linux-foundation-easycla]

• ❌ - login: @blueberryapple . The commit (3cbe11f) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[eslint-github-bot]

Hi @blueberryapple!, thanks for the Pull Request

The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.
• The first letter of the tag should be in lowercase

To Fix: You can fix this problem by running git commit --amend, editing your commit message, and then running git push -f to update this pull request.

Read more about contributing to ESLint here

[netlify]

✅ Deploy Preview for docs-eslint canceled.

Name	Link
🔨 Latest commit	3cbe11f
🔍 Latest deploy log	https://app.netlify.com/sites/docs-eslint/deploys/62e0c3641a80df00085611b0

[eslint-github-bot]

Hi @blueberryapple!, thanks for the Pull Request

The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.
• The first letter of the tag should be in lowercase

To Fix: You can fix this problem by running git commit --amend, editing your commit message, and then running git push -f to update this pull request.

Read more about contributing to ESLint here

[harish-sethuraman]

This was intentional we didn't want to add all package managers for initializing the config. #16084 (comment)

[blueberryapple]

Then we should probably remove the yarn command here too:

eslint/docs/src/user-guide/getting-started.md

Lines 35 to 43 in 3cbe11f

	After that, you can run ESLint on any file or directory like this:
	```shell
	npx eslint yourfile.js
	# or
	yarn run eslint yourfile.js
	```

[harish-sethuraman]

Yea good catch, may be we can remove it. But would like to hear from others as well :)

[nzakas]

The installation case is different than the execution case. For installation, the command will ask if you want to install using npm, yarn, pnpm, etc. so it doesn’t really matter how you run it. I think for executing eslint it make sense to also mention yarn.

[nzakas]

We purposely left this out, so closing.