Update the DEV.md about the creation of PAT

[Sahityaaryan]

The DEV.md is not updated with the new methods of generating the tokens and lack clarity about those methods of generating PAT so that an acceptable PAT can be generated, (which actually works after pasting it in the command)

This leads to repeated errors while setting up the project and it may lead to waste of a significant amount of time.

[DhairyaMajmudar]

Facing the same issue while setting up the repo in my Debian based Linux system, After Doing little changes with the command to worked fine npm.pkg.github.com/:_authToken=[YOUR_GITHUB_PERSONAL_ACCESS_TOKEN] this was that changes.

@meganindya pls. oversee this command if it is okay I will generate a pr closing this issue.
Thanks!

[RAGHAV-N5]

Hey, I have found a solution to this problem, we need to paste //npm.pkg.github.com/:_authToken[YOUR_GITHUB_PERSONAL_ACCESS_TOKEN]
@sugarlabs:registry=https://npm.pkg.github.com
in the .npmrc file and save it
[YOUR_GITHUB_PERSONAL_ACCESS_TOKEN] instead of this please replace it with your PAT.
If you face any further problems please don't hesitate to discuss it!

[kaurjasleen240305]

Hey @meganindya also I did this to solve above problem I generated classic PAT rather than fine grained PAT to recover this problem in which scopes I gave read:access to PAT

[Akshanshkaushal]

@Sahityaaryan I would love to work upon this . kindly assign this? or should I start working upon on this