Fix: NPM GH release publishing should set latest

[jackw]

What Changed

Updated the NPM plugin to set nextRelease flag when calling git.publish.

Why

It looks like GH releases in the NPM plugin aren't using the nextRelease flag that was introduced in #2391

fixes: #2422

Todo:

• Add tests
• Add docs

Change Type

Indicate the type of change your pull request is:

• documentation
• patch
• minor
• major

[codecov]

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (7a6f0ae) 85.92% compared to head (fce0e96) 80.58%.

Files	Patch %	Lines
plugins/npm/src/index.ts	0.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2423      +/-   ##
==========================================
- Coverage   85.92%   80.58%   -5.34%     
==========================================
  Files          69       69              
  Lines        5675     5675              
  Branches     1332     1274      -58     
==========================================
- Hits         4876     4573     -303     
- Misses        718      719       +1     
- Partials       81      383     +302     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jazmon]

Seems like a duplicate of my fix #2414

[hipstersmoothie]

@jackw or @jazmon I think the logic in your PRs should be combined

[jazmon]

@hipstersmoothie I combined the contents from this PR to my PR if you could have a look 🙏 #2414

[jackw]

Let's close this as @jazmon has gone to the trouble of bringing the two together. Awesome work everybody! 🚀