ci(actionlint): fix the errors produced by the ActionLint tool #95

ci(actionlint): fix the errors produced by the ActionLint tool

Usage Workflow file

10 errors and 1 warning

actionlint: .github/workflows/.dast-nuclei-cmd-api-server.yaml#L53

shellcheck reported issue in this script: SC2129:style:2:1: Consider using { cmd1; cmd2; } >> file instead of individual redirects

actionlint: .github/workflows/.dast-nuclei-cmd-api-server.yaml#L86

shellcheck reported issue in this script: SC2005:style:1:6: Useless echo? Instead of 'echo $(cmd)', just use 'cmd'

actionlint: .github/workflows/.dast-nuclei-cmd-api-server.yaml#L92

shellcheck reported issue in this script: SC2005:style:1:6: Useless echo? Instead of 'echo $(cmd)', just use 'cmd'

actionlint: .github/workflows/.dast-nuclei-cmd-api-server.yaml#L95

shellcheck reported issue in this script: SC2005:style:1:6: Useless echo? Instead of 'echo $(cmd)', just use 'cmd'

actionlint: .github/workflows/actionlint.yaml#L60

shellcheck reported issue in this script: SC2242:error:8:6: Can only exit with status 0-255. Other data should be written to stdout/stderr

actionlint: .github/workflows/besu-all-in-one-publish.yaml#L44

shellcheck reported issue in this script: SC2021:info:6:34: Don't use

actionlint: .github/workflows/besu-all-in-one-publish.yaml#L44

shellcheck reported issue in this script: SC2021:info:6:42: Don't use

actionlint: .github/workflows/besu-all-in-one-publish.yaml#L44

shellcheck reported issue in this script: SC2193:warning:10:24: The arguments to this comparison can never be equal. Make sure your syntax is correct

actionlint: .github/workflows/besu-all-in-one-publish.yaml#L44

shellcheck reported issue in this script: SC2001:style:10:57: See if you can use ${variable//search/replace} instead

actionlint: .github/workflows/cacti-dev-container-vscode-publish.yaml#L49

shellcheck reported issue in this script: SC2021:info:6:34: Don't use

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