ci: upgrade to actions/checkout@v3

[LaszloGombos]

It resolves the following warning:
Please update the following actions to use Node.js 16: actions/checkout

[johannbg]

LGTM

[johannbg]

Maybe we should have dependabot handle this CI task for us in the future ( or implement it now and see it working )

1. https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot

[iammattcoleman]

@johannbg Is it possible to configure dependabot to not upgrade some tests? In order to get the manual tests working in the Gentoo container, I had to revert to actions/checkout@v1 in this commit:
ef9ccd5

This is due to version v2+ of the runner using a hardcoded path for an externally-provided node binary, but the provided binary not being compatible with Gentoo:
actions/runner#2115

[johannbg]

@iammattcoleman it has allow/ignore: see [1] not sure if it works thou but honestly if gentoo is becoming too much trouble than it's worth and a security risk then we simply drop it and focus on something that costs less and makes our lives easier.

1. https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#allow

[LaszloGombos]

Marked as draft in favor of testing #2016 .

[LaszloGombos]

Closing to take it out from active PR list. Will reopen if it becomes necessary.

[LaszloGombos]

Reopening for review

[johannbg]

Let's merge this and close the other one

[LaszloGombos]

@aafeijoo-suse Would you be able to help with the review of this PR ?

[aafeijoo-suse]

@aafeijoo-suse Would you be able to help with the review of this PR ?

I don't know how I can help review this change, I'm not an expert on GitHub proprietary stuff and most of the time it just shows issues after the merge.

[LaszloGombos]

and most of the time it just shows issues after the merge.

This is a fair statement. Please note:

• https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/
• The way I read this is that around "Summer 2023" our CI might stop because of this..So there is plenty of time
• I found a way to do a test run for this change - https://github.com/LaszloGombos/dracut/actions/runs/3445182730/jobs/5748600774 (note the "Run actions/checkout@v3" step under "Checkout Repository")
  - If somehow there is still an issue after the merge, revert is always an option...

So the decision really is try to land or wait until it will be broken for sure..