Update Troubleshooting in Package Registry docs

Open Minaro requested to merge MinaroShikuchi/gitlab:MinaroShikuchi-master-patch-04624 into master

What does this MR do?

Based on this issue #361608 (closed), the docs is a bit unclear about how to install npm package registry from CI job. IMHO this needs to be added to the docs to help troubleshooting.

Related issues

gitlab-foss#61109 (closed)

#361608 (closed)

https://stackoverflow.com/questions/71362296/gitlab-package-registry-throw-404-on-npm-publish

Forum

https://forum.gitlab.com/t/npm-install-from-gitlab-package-registry-not-working/45754

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • Ensure a release milestone is set.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Edited by Minaro