build: upgrade to node20 for gha

Thank you for submitting this pull request

Fixes the following Warning:

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: kiegroup/git-backporting@v4.5.1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Description

Upgrade the GHA node version to 20.

How Has This Been Tested?

CI workflows now run on three different node versions: 16, 18 and 20.

Checklist

[ ] Tests added if applicable.
[ ] Documentation updated if applicable.

Merge criteria:

[x] The commits and have meaningful messages; the author will squash them after approval or will ask to merge with squash.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

Note: dist/cli/index.js and dist/gha/index.js are automatically generated by git hooks and gh workflows.

First time here?

This project follows [git conventional commits](https://gist.github.com/qoomon/5dfcdf8eec66a051ecd85625518cfd13) pattern, therefore the commits should have the following format: ``` (): empty separator line empty separator line ``` Where the type must be one of `[build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test]` > **NOTE**: if you are still in a `work in progress` branch and you want to push your changes remotely, consider adding `--no-verify` for both `commit` and `push`, e.g., `git push origin --no-verify` - this could become useful to push changes where there are still tests failures. Once the pull request is ready, please `amend` the commit and force-push it to keep following the adopted git commit standard.

How to prepare for a new release?

There is no need to manually update `package.json` version and `CHANGELOG.md` information. This process has been automated in [Prepare Release](./workflows/prepare-release.yml) *Github* workflow. Therefore whenever enough changes are merged into the `main` branch, one of the maintainers will trigger this workflow that will automatically update `version` and `changelog` based on the commits on the git tree. More details can be found in [package release](https://github.com/kiegroup/git-backporting/blob/main/README.md#package-release) section of the README.

Coverage report

St.^{:grey_question:}	Category	Percentage	Covered / Total
🟢	Statements	91.13% (+0.31% 🔼)	421/462
🟢	Branches	84.69% (+0.51% 🔼)	166/196
🟢	Functions	89.83% (+1.6% 🔼)	106/118
🟢	Lines	91.11% (+0.36% 🔼)	410/450

Show files with reduced coverage 🔻

St.^{:grey_question:}

| File | Statements | Branches | Functions | Lines | | :-: | :- | :- | :- | :- | :- | | 🟢 |

`...` / configs-parser.ts

91.67% (-8.33% 🔻)

83.33% (-16.67% 🔻)

| 100% |

91.67% (-8.33% 🔻)

| | 🟢 | runner/runner.ts |

87.04% (-1.85% 🔻)

90.91% (-1.4% 🔻)

75% (-5% 🔻)

87.04% (-1.85% 🔻)

Test suite run success

168 tests passing in 16 suites.

Report generated by 🧪jest coverage report action from c57329144140b767a4ad5fc3ebc77795028658b0

kiegroup / git-backporting