feat: Adding publicPath option for npm publishConfig

[xllily]

Adds the publicPath option to the npm.publishConfig configuration item to facilitate custom configuration and meet the needs of users in certain scenarios.

At present, after npm publish succeeds, the npm package address displayed in the terminal printout log is https://{{host}}/package/{{packageName}}, through this publicPath option allows /package replace it with a custom path.

For example, when using a third-party tool Verdaccio to build an npm private proxy , The package address of Verdaccio web user interface is fixed and cannot be configured https://{{host}}/-/web/detail/{{packageName}}, In this case, npm.publishConfig.publicPath can can be configured as -/web/detail.
Then the terminal will print the address https://{{host}}/-/web/detail/{{packageName}} after npm publish done , the user can directly click on the npm package address printed in the terminal output log to access the web user interface of Verdaccio, enhanced user experience.

[webpro]

Thanks @xllily! Any chance you could add a unit test for this (or extend an existing test), so your changes will have some coverage?

[xllily]

Thanks @xllily! Any chance you could add a unit test for this (or extend an existing test), so your changes will have some coverage?

@webpro :

Thank you for your valuable feedback. I have taken your suggestion into consideration and have added a unit test for the changes I made. The unit test has been successfully incorporated into the existing test suite to ensure proper test coverage.

I genuinely appreciate your guidance in maintaining the quality of the code. If there are any other modifications or additions you would like me to make, please don't hesitate to let me know. I am more than willing to assist and address any concerns you may have.

[webpro]

Excellent, thanks again!

[webpro]

🚀 This pull request is included in v15.11.0. See Release 15.11.0 for release notes.