[BUG] npm install command without specific dependency re-orders entire lockfile

Current Behavior:

When running npm install with no specific dependency listed package-lock.json gets updated and the ordering of dependencies is changed. This causes us to constantly be accidentally committing changes to this file when there are in-fact, no changes.

It also makes it incredibly difficult to properly see how things have changed over time, and introduces another fun event, which is that running npm install @sentry/browser@latest (or any package) will then cause the lockfile to get re-ordered and it returns to alphabetical order in the dependency listing (and thus re-arranges all of the lockfile.

Expected Behavior:

I would expect that running npm install without a dependency would not modify the lockfile to be randomly ordered unless it was actually updating a dependency.

Steps To Reproduce:

1. Run npm install and see that the lockfile changes order.
2. Run npm install some-dependency and see that package-lock.json returns to it's initial ordering with the new dependency injected as expected.
3. Run npm install again and see package-lock.json changes ordering again.

Environment:

OS: macOS Big Sur (11.1)
node: 15.8.0
npm: 7.5.1 7.5.6

Reproduce the ordering changes with npm 7.5.6 using the listed npm install steps and inspect the resulting package-lock.json. Then trace the npm CLI lockfile handling involved in installs with and without a dependency. Done means an install with no dependency changes leaves lockfile ordering unchanged, while dependency updates still produce the expected lockfile changes and regression coverage verifies both cases.