The "Create Pull Request" action force-pushes to the branch, even if nothing has changed since last, which cause unnecessary runs and unwanted strain on CI.

Ideally, we'd want the workflow to "back off" if running the update doesn't produce a different package-lock.json than what's on the branch. This would also allow for us to push follow-up commits to the "update PR branch" to fix any breakage, without risking a force-push negating these (as long as we're not updating the package-lock).