Update dependencies, Github achtions and dependabot strategy

[mahula]

Proposed changes

• Pin github actions to current commit hash
  Pinning Github actions is one measure against supply-chain attacks, see https://blog.rafaelgss.dev/why-you-should-pin-actions-by-commit-hash
• Update package patch versions
• Reset dependabot strategy
• Set nodejs version to current lts version

Types of changes

What types of changes does your code introduce ?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)
• Update of dependencies, Github achtions,and dependabot strategy

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[8BitJonny]

Thanks @mahula and sorry for the late reply. I'll have a look at it on the weekend but at a first glance I think this can be incorporated right away into the next version

[8BitJonny]

I don't want to check whether all commit hashes of the actions match or not, if the first hash doesn't match.
So thanks for your submission, but I'll do it myself, since I also don't want to change the dependabot config like you proposed

[8BitJonny]

That is not true?
v4.2.2 has the hash 11bd71901bbe5b1630ceea73d27597364c9af683
actions/checkout@11bd719

[mahula]

No,
what the comment at the line's end represents is the most current release version of the used action, while in the workflow the latest commit has is used.

Why did you close the whole PR, @8BitJonny ?
The commit hashes were just one of several changes to the action.