build(deps): bump reactive-firewall/shellcheck-scan from 1 to 2

[dependabot]

Bumps reactive-firewall/shellcheck-scan from 1 to 2.

Release notes

Sourced from reactive-firewall/shellcheck-scan's releases.

Version v2.0

Patch Notes

• This version enhances overall stability, and migrates several components to newer implementations.

[!IMPORTANT]

🔧 Breaking changes in v2.0

Due to the underlying implementation of GitHub's Code-Scanning Dashboard, some users will see warnings about shellcheck scan workflow configuration(s). These warnings are unavoidable when upgrading to the new v2.x series for the first time. See below for details and recommended resolution.

Impacted GHI

• Closes #6
• Closes #16

Included and Superseded PRs/MRs

• Includes and supersedes #12
• Includes and supersedes #13
• Includes and supersedes #14
• Includes and supersedes #15

v2.0 Migration Troubleshooting

[!TIP] Users who previously used v1 will need to migrate to using v2 to benefit from this, and future updates.

Previous tool "configuration" is "out of date" after upgrade

[!WARNING] After initially upgrading from version v1 series of shellcheck-scan, users will see shellcheck-scan configuration warnings, namely about legacy ad-hoc configurations. New setups (including full remove-then-re-setup workflows) should not normally encounter these warnings

When encountering configuration "is out of date" warnings for shell-check, no historical data is destroyed by default. GitHub should continue to retain the scan data as normal according to your GitHub plan. However unless you named everything exactly shellcheck-scan in your workflow config, everything before upgrading will be marked as now being "out-of-date".

E.g., You will likly see the warning all over the GitHub Security tab in the Web UI.

Once you are ready to clear out historical results (e.g., after they have been fixed, or perhaps as soon as the latest scan, etc.)

1. Navigate to the Code scanning tools, for example from the warning itself:

2. Then navigate to the out-of-date shellcheck tool (note: in some cases, it may even have been called something other than "shellcheck-scan" before)

3. Open the tool configuration

... (truncated)

Commits

• 50ac9fb SECURITY -- Resolve GHI #19
• 05d6614 Minor fix for GHI #18
• 434ca8b Release candidate for version v2.0 (v2.0-rc3)
• cff470c Fix backported for MIT Licensed tool (from upstream)
• 15be86b [HOTFIX] Possible fix for GHI #16
• 75d2eaa 2nd Release Candidate for Version 3.0 (v3.0-rc2)
• 7f54f0c [UPDATE] Version bump requests to current latest
• dcb2c0c Update to support additional transformation options (updated shell aliases)
• d20f433 Improved shell options for MIT Licensed tool (from upstream)
• 0ffc240 Merge pull request #15 from reactive-firewall/dependabot/github_actions/maste...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.