Allow Updating package.lock file through Actions

[garrettmflynn]

An attempt to fix issues when we push an M1 / M2 package.lock file (#598, #597)

[CodyCBakerPhD]

Also

An attempt to fix issues when we push an M1 / M2 package.lock file (#598, #597)

What does this PR have to do with those previous problems? We're not running into a currently problem with building the app in the distributable/releasable sense are we?

The first PR had to do with M1 specifically (our current issue is with non-M1/M2) and the second PR was the conda environment and is unaffected by the npm side

[garrettmflynn]

Both of those issues had aspects that were / would have been broken before #605, which would be reversed by pushing a compromised package-lock.json from (at least) my M2—which we want to update somehow to test if that fixes the blocked tests we observe now.

[CodyCBakerPhD]

Hah, IDK - even npm install might be running into issues now: https://github.com/NeurodataWithoutBorders/nwb-guide/actions/runs/8287280865/job/22679223021?pr=673

[CodyCBakerPhD]

Added verbosity: seems to stall at this line: https://github.com/NeurodataWithoutBorders/nwb-guide/actions/runs/8287381363/job/22679580477?pr=673#step:4:1865

[CodyCBakerPhD]

replaced by #678