Remove `--frozen-lockfile` for pnpm deps installation in document

[SnO2WMaN]

Description:

In below documents pnpm install --frozen-lockfile, but pnpm passes the --frozen-lockfile option automatically when it detects that it is running on CI (i.e. on GitHub Actions).

setup-node/docs/advanced-usage.md

Lines 246 to 266 in a4fcaaf

	**Caching pnpm (v6.10+) dependencies:**
	```yaml
	# This workflow uses actions that are not certified by GitHub.
	# They are provided by a third-party and are governed by
	# separate terms of service, privacy policy, and support
	# documentation.
	# NOTE: pnpm caching support requires pnpm version >= 6.10.0
	steps:
	- uses: actions/checkout@v3
	- uses: pnpm/action-setup@v2
	with:
	version: 6.32.9
	- uses: actions/setup-node@v3
	with:
	node-version: '14'
	cache: 'pnpm'
	- run: pnpm install --frozen-lockfile
	- run: pnpm test
	```

I thought it seems that it is better not to pass it explicitly in document, so as not to cause unnecessary confusion.

References

• https://pnpm.io/cli/install#--frozen-lockfile
• https://github.com/watson/ci-info#supported-ci-tools

Are you willing to submit a PR?

Yes

[dmitry-shibanov]

Hello @SnO2WMaN. Thank you for your suggestion. Do these changes apply to pnpm 6.10+ versions ?

[SnO2WMaN]

Hello @SnO2WMaN. Thank you for your suggestion. Do these changes apply to pnpm 6.10+ versions ?

At least works in pnpm v7, and perhaps even works in v6.

[dmitry-shibanov]

Hello @SnO2WMaN. I'm going to close the feature request because we've updated the documentation in scope of this pull request: #789