fix(repo): update lock file after dependabot to use npm 11

[mandarini]

Problem

• Every time dependabot updated package-lock.json, it used npm@10 which changed the lock file
• Every time publish.yml runs, it uses npm@latest (now 11) so that we can use trusted publishing. This means that it gets diffs in the lock file.

Solution

• Add workflow to auto-regenerate lockfile on Dependabot PRs with npm@latest
• Fixes recurring CI failures in publish.yml caused by npm version mismatch (Dependabot uses npm 10, publish uses npm 11)

[coveralls]

coverage: 80.691% (-0.5%) from 81.176%
when pulling b9da960 on fix/dependabot-and-lock
into 87e19a3 on master.

[staaldraad]

booooo dependabot 👎🏼
https://docs.github.com/en/code-security/dependabot/working-with-dependabot/dependabot-options-reference#package-ecosystem-
states "supported versions: v7,v8,v9,v10" - wish this was configurable through the dependabot.yml

[mandarini]

You can specify npm version with renovate I think. But it's ok, I hope this fix fixes the issue. :(