fix(npm): mark releases as latest with lerna

[jazmon]

What Changed

Mark the releases as "latest" when releasing with the npm plugin with the independent mode.

Why

Currently auto gets the latest release by looking for a release that is marked as "latest". The npm plugin does not update the "latest" tag when releasing with independent mode causing the releases to start diffing from the initial release.

Todo:

• [X] Add tests
• [x] Add docs

Change Type

Indicate the type of change your pull request is:

• [ ] documentation
• [X] patch
• [ ] minor
• [ ] major

[TUNER88]

@intuit any chance to get it merged? Having same problem causing incorrect change logs and version numbers

[codecov[bot]]

Codecov Report

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

Comparison is base (432e152) 80.65% compared to head (a55aac0) 80.57%. Report is 6 commits behind head on main.

Files	Patch %	Lines
plugins/npm/src/index.ts	0.00%	1 Missing and 2 partials :warning:

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2414      +/-   ##
==========================================
- Coverage   80.65%   80.57%   -0.09%     
==========================================
  Files          69       69              
  Lines        5676     5677       +1     
  Branches     1274     1275       +1     
==========================================
- Hits         4578     4574       -4     
- Misses        718      719       +1     
- Partials      380      384       +4     

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[jazmon]

Looks like it's passing the CI checks! (other than the two that seem to have some other issues)

Anything preventing from releasing this?

[github-actions[bot]]

:rocket: PR was released in v11.0.7 :rocket: