Update package-lock to try to unstick dependabot

[maribethb]

The basics

• I branched from develop
• My pull request is against develop
• My code follows the style guide

The details

Resolves

All of the dependabot changes have been stuck for a few days with cryptic errors. The internet suggests deleting and regenerating the package lock, which actually upgrades the dependency versions. I've done that here to see if it can kick dependabot back into working.

I kept eslint the same version so we'd have a test case for a dependabot version. But the mocha and generator tests also failed to run for me locally so I also kept webdriverio the same version.

So the versions changed are all the other ones in this list that are NOT major bumps: https://github.com/google/blockly/pulls?q=is%3Apr+is%3Aopen+label%3Adependencies

@blockly/dev-tools, trim-newlines, etc

Test Coverage

Tested with

npm run build
npm run start
npm run test

Tests intermittently fail with php generator errors, this seems unrelated.

Also, I made eslint stay on the old version instead of updating. That way we could try rebasing this PR and see if it works: #5116

Additional Information

I think this started happening after #5038 so if this doesn't work we may need further investigation there.