Edit authenticate-packages.md

[johann1301s]

It is confusing as to why you would need a login token when accessing a public package. Shouldn't the pointer in the local .npmrc file be enough? I.e @<scope>:registry=https://npm.pkg.github.com.

This change should make things clearer. Notice from the two posts linked here show that I am not alone in finding the need for the token strange.

"This is an public package.Is it should be auth too?" - from post.

Stack overflow issues:

https://stackoverflow.com/questions/73247706/unable-to-install-public-npm-package-from-github-package-registry-using-github-a?noredirect=1#comment129360034_73247706

https://stackoverflow.com/questions/60491581/installing-public-npm-packages-from-the-github-package-registry/73253496#73253496

---

Please feel free to modify how I changed the sentence, but make it explicit that the token regards both private AND public packages.

[welcome[bot]]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[cmwilson21]

@johann1301s Thanks so much for opening a PR! I'll get this triaged for review :zap:

[johann1301s]

Forgive me, but I asked a new question on stack overflow related to this:

https://stackoverflow.com/questions/73262134/why-are-personal-access-tokens-necessary-to-install-public-github-packages

[vgrl]

Thanks @johann1301s ⚡, I'm going to make a small edit, and then I'll merge this.

[github-actions[bot]]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues :zap: