Update the `corepack enable` prerequisite to latest approach for installing `pnpm` as used in cookieplone templates

[acsr]

In the linked line the resolution for recent issues with pnpm and how they can be resolved is not reflected:
https://github.com/plone/documentation/blame/a9d545efb96ba2c466db2a69c724294d5f7ebff6/docs/install/create-project-cookieplone.md#L101

In current cookieplone we replaced all occurences related to install pnpm and corepack enable were changed from corepack enable to:

npm i -g corepack@latest && corepack enable

see: plone/cookieplone-templates#162
and: https://community.plone.org/t/corepack-problems-specially-in-ci/20597

@ksuess mentioned this docs as reference with no need to change in this ticket comment: plone/training#925 (comment)
But I guess the pitfall with pnpm still remains if not updating this prerequisite here.

Why should it be changed?

• It is hard for insiders to discover the situation if your setup already satisfies the prerequisites.
• I was struggling with the old cookiecuter-plone-starter while that relied on yarn and no one could reproduce my challenge at that time.

[stevepiercy]

I'm not altogether certain that we should replace the command everywhere.

1. Error during first steps in Mastering Plone 6 development (backend) training#925 (comment) indicates there is no issue now. @sneridagh @davisagli can you advise on using corepack enable in this step https://6.docs.plone.org/install/create-project-cookieplone.html#node-js ? Is npm i -g corepack@latest && corepack enable a permanent workaround, or something that will be resolved in an update, allowing us to use just corepack enable? If I did corepack enable on my local machine before this issue arose, will I be OK? In other words, does this issue affect only those people who have not yet enabled corepack on their development environment? I can't verify this because of an unrelated issue.

   EDIT: using the workaround 2 in the linked unrelated issue allowed me to verify that I did not need to issue either corepack enable or npm i -g corepack@latest && corepack enable to get it to build. That leads me to believe that it only affects users and CI where neither command was used at least once before. Indeed, the following version checks confirm I already had corepack installed before.

   $ node -v            
   v20.10.0
   $ corepack -v
   0.22.0

2. cookiecuter-plone-starter is deprecated. The only reason we keep it around is to inform users that it is deprecated, and Cookieplone should be used instead for all new projects. If you use it for new projects, you are on your own. I'm inclined to gut the contents of this page, and leave only the warning to prevent leading users astray.

3. The command in the Glossary should be purged because it lacks context and is redundant to when it would have context elsewhere.

4. There is an instance of corepack enable in the Volto Upgrade Guide for v16.x.x that I am uncertain about. See upgrading to Volto 16.x.x. @sneridagh can I get your opinion on this one? It's a tiny change that might help a few stragglers, so I'm OK with changing it. This would need to be done in the Volto repo.

[ksuess]

pnpm installation instructions https://pnpm.io/installation#using-corepack are recommending

npm install --global corepack@latest
corepack enable pnpm

by mentioning the issue with outdated signatures in Corepack
which seems to be not only a temporary issue and not already solved.

So it seems to be time to reflect this in the documentation.

---

BTW
I didn't make myself clear in plone/training#925 (comment). I'm just saying that instructions, e.g. for installing pnpm, should be written down in one place to avoid redundancy. Redundancy quickly leads to differing statements.
Therefore the training material is referencing docs.plone.org

[stevepiercy]

Thanks for the authoritative reference @ksuess.

I think we should do the following.

1. Update the command. Create a new issue to track the status of the upstream fix in Newly published versions of package managers distributed from npm cannot be installed due to key id mismatch nodejs/corepack#612, at which time we can consider undoing this verbose command. I'll create the new issue here.
2. Leave it as is. It's deprecated. Consider gutting the page content except for the admonition. That should be another discussion in another issue. I'll create it.
3. Remove the command.
4. Leave it, unless @sneridagh says to update it.

I'll revisit the PR from @Manas-Kenge in #1879 and update it accordingly.

[stevepiercy]

pnpm installation instructions https://pnpm.io/installation#using-corepack are recommending

npm install --global corepack@latest
corepack enable pnpm

Per the Info admonition at that link.

info

If you have installed Node.js with pnpm env Corepack won't be installed on your system, you will need to install it separately. See #4029.

We don't tell people to do that, but instead to use the following, per https://6.docs.plone.org/install/create-project-cookieplone.html#node-js

nvm install --lts
nvm use --lts

I think it is safe to skip the second command. Would you agree @ksuess?

[sneridagh]

@acsr @stevepiercy @ksuess

There was a problem with one version of corepack that was included in the latests Node.js versions.
Now this error is fixed for latest 22 (22.14.0), but unfortunatelly, they didn't include it in latest 20 :(

So, in summary, I think that it's ok that we update the command to upgrade in the first place.
However, this solution works today. Tomorrow one does not know if upgrading to corepack to latest in all situations would be safe, eg. latest corepack is not compatible with "old" Node X.x...

So I'm a bit undecided on this one. We could say that the problem is solved for latest 22, but point people to the problem and it's solution too. My guess is that at some point, Node 20 will include also the latest corepack so it will be fixed in there. Of course, only if you will have up to date your Node versions everywhere (in CI too).

[ksuess]

nvm install --lts
nvm use --lts

I think it is safe to skip the second command. Would you agree @ksuess?

Yes, nvm install --lts already activates the installed node version.

[sneridagh]

nvm use --lts

@stevepiercy this is necessary

[sneridagh]

@ksuess is that so? I thought it was not "using" it. @ksuess we posted at the same time :)

[ksuess]

nvm use --lts

@stevepiercy this is necessary

OK. I thought i remember a log feedback something like. " now using…"
But ok