ci: Update .lock files in dependabot PRs

[witwash]

Summary

Added a follow-up action to commit .lock files if PR was created by the dependabot.

Testing steps

Dependabot PR should trigger this action and changes in .lock should be committed.

Follow-up issues

None

Check during review

• Verify against Jira issue.
• Is the PR over 300 additions? Consider rejecting it with advice to split it. Is it over 500 additions? It should definitely be rejected.
• Unused code removed.
• Build passing.
• Is it a bug fix? Check that it is covered by a proper test (unit or integration).

[witwash]

@ookami-kb,
looks like dependabot is updated and this one is not needed anymore #489

[witwash]

@ookami-kb, what do you think?

[ookami-kb]

In general, yeah, makes sense, let's try it this way.

[witwash]

If this one is true,

When a Github Actions workflow is configured to run on pull requests, by default it will be triggered on three different types of activities: opened, synchronize, and reopened.

then by default, this action would be triggered on opened, reopened, and synchronize. But I could not find it in the docs and decided to define it explicitly.