fix: fix strict-ssl mapping for node-fetch-registry during unpublished projects lookup

[CSchulz]

fixes #3746

Description

There is a missing mapping of strict-ssl for unpublished projects lookup.
This results into falsy unpublished projects.

Motivation and Context

We are using lerna to automatically determine which packages are unpublished. We have encountered the issue it tries to publish packages again and again regardless if they are already published.
With debugging I have found out there is an issue using the given strict-ssl attribute. It is not passed to pacote correctly.

In general it is the same issue like here #2952

How Has This Been Tested?

I have debugged everything and also tried to write an unit test which should cover this scenario.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (change that has absolutely no effect on users)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
  • there are some tests failing (perhaps of my Windows environment)

[nx-cloud]

☁️ Nx Cloud Report

Attention: This version of the Nx Cloud GitHub bot will cease to function on July 1st, 2023. An organization admin can update your integration here.

We didn't find any information for the current pull request with the commit a21415a.
You might need to set the 'NX_BRANCH' environment variable in your CI pipeline.

Check the Nx Cloud Github Integration documentation for more information.

---

Sent with 💌 from NxCloud.

[JamesHenry]

Thanks @CSchulz, please run npm run format:write and commit the results, the formatting check is currently failing

[JamesHenry]

Thanks!