feat: additional arguments publishArgs and versionArgs for npm commands

[1aron]

• fix: Execute npm version with --workspaces=false #512
• fix: add --no-workspaces to npm whoami #529

I built my own monorepo ecosystem based on semantic release.

During the NPM release process, I encountered resistance, so I added two conservative features.

Since specifying a workspace in .npmrc such as workspace=packages will change the behavior of executing npm run in the root directory, we usually don't want to store .npmrc, and NPM will not automatically read the .workspaces settings in package.json when running npm publish and npm version, which is quite inconvenient.

Of course, we can execute echo -e "\nworkspace=packages/**/*" >> .npmrc on CI, but as mentioned above, it will affect the execution of subsequent instructions, which will make the command of the project not predictable.

Before submitting this PR I removed @semantic-release/npm package and solved my problem in publishCmd:

{
     "publishCmd": "npm publish --workspace=packages"
}

But I found that I was missing a lot of the benefits that @semantic-release/npm brought me.

You can see the use cases I added in the README:

{
     "publishArgs": ["--workspace", "packages"],
     "versionArgs": ["--workspace", "packages"]
}

These test cases were failing before I made any changes:

I even use it on the Master CSS open source project, which is a monorepo, and it works nicely with Semantic Release.

This is not a monorepo-specific feature, but this can be very useful in monorepo projects with multiple packages. Hope this feature passes quickly, thanks to the Semantic Release team for all you do.

[1aron]

I've published my changes as aron-semantic-release-npm and it works perfectly fine in practice:

https://github.com/1aron/aronrepo/actions/runs/3645164693/jobs/6155064392#step:6:275