Bump codacy/codacy-analysis-cli-action from 1.1.0 to 4.0.0

[dependabot]

Bumps codacy/codacy-analysis-cli-action from 1.1.0 to 4.0.0.

Release notes

Sourced from codacy/codacy-analysis-cli-action's releases.

Parallel mode runs now tools in parallel

Parallel mode was not working as intended. Now it spawns multiple Docker instances based on the parallelism level

Fix using the correct commit SHA on pull requests

Actions triggered on pull requests now send the reports for the correct commit SHA

Fix staticcheck flow that could change go.mod files

No release notes provided.

Fix standalone tools

Fixes scenario where gosec does not run leading to failure in the next standalone tools.

Add support for account API tokens

No release notes provided.

Fix SARIF output for tools that returns 0 startLine

No release notes provided.

Bump CLI version used in action

• Bump to CLI version to 5.1.4.
• Now, when exporting issues to SARIF it no longer downgrades issues' severities for security patterns.

Commits

• 0de7704 Merge pull request #63 from codacy/bump-cli-to-7.0.0
• c546f3f bump: Bump codacy-analysis-cli to 7.0.0
• b3451bc Merge pull request #60 from codacy/fix/use-correct-commit-sha
• 6be6304 fix: Propagate the correct commit-uuid to the codacy-cli CY-4321
• 899bdc4 Bump codacy-analysis-cli version
• b848abd fix: Use commit SHA from the event CY-4321
• 9d53f2c Merge pull request #59 from codacy/fix/keep-changes-go-mod
• 1e61a71 style: Change backup file extension
• 3f110ef fix: Fix possible changes to users' go.mod files CY-4272
• 21691b3 Merge pull request #58 from codacy/fix/reset-changes-go-mod
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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-actions]

Here are some friendly prose warnings from write-good:

In ./README.md
=============
By default (without any additional options) this formula install the
                        ^^^^^^^^^^
"additional" is wordy or unneeded on line 16 at column 24
-------------
haviour or add even more stuff.
                         ^^^^^
"stuff" can weaken meaning on line 18 at column 54
-------------
ds all Commandline tools are installed.
                         ^^^^^^^^^^^^^
"are installed" may be passive voice on line 27 at column 59
-------------
 =--HEAD= builds are not really supported. They may fail to install,
                         ^^^^^^
"really" can weaken meaning on line 29 at column 34
-------------
Many thanks to everyone reporting issues.
^^^^
"Many" is a weasel word and can weaken meaning on line 47 at column 0


In ./CODE_OF_CONDUCT.md
=============
The qtifw community is made up of members from around the globe with a diverse s
                    ^^^^^^^
"is made" may be passive voice on line 3 at column 20
-------------
lities, and experiences. It is through these differences
                         ^^^^^
"It is" is wordy or unneeded on line 3 at column 126
-------------
ronment where anyone can participate and everyone can make a difference.
                         ^^^^^^^^^^^
"participate" is wordy or unneeded on line 13 at column 32
-------------
oftentimes their labor was completed simply for the good of the community. We're
                       ^^^^^^^^^^^^^
"was completed" may be passive voice on line 18 at column 23
-------------
heir labor was completed simply for the good of the community. We're attentive i
                         ^^^^^^
"simply" can weaken meaning on line 18 at column 37
-------------
Overall, we're good to each other. We contribute to this community not because w
^^^^^^^
"Overall" is wordy or unneeded on line 27 at column 0
-------------
 everyone. Our community is based on mutual respect, tolerance, and encouragemen
                         ^^^^^^^^
"is based" may be passive voice on line 32 at column 85
-------------
specific attributes that are used to
                         ^^^^^^^^
"are used" may be passive voice on line 38 at column 147


In ./.github/ISSUE_TEMPLATE.md
=============
sted information. If you repeatedly fail to use the issue template, we will bloc
                         ^^^^^^^^^^
"repeatedly" can weaken meaning on line 1 at column 177


In ./.github/ISSUE_TEMPLATE/feature_request.md
=============
**Additional context**
  ^^^^^^^^^^
"Additional" is wordy or unneeded on line 18 at column 2


In ./.github/ISSUE_TEMPLATE/bug_report.md
=============
**Additional context**
  ^^^^^^^^^^
"Additional" is wordy or unneeded on line 39 at column 2


In ./.github/PULL_REQUEST_TEMPLATE.md
=============
-   [ ] Have you successfully run 'brew tests' with your changes locally?
                 ^^^^^^^^^^^^
"successfully" can weaken meaning on line 5 at column 17