fix issue with analysis using tool configuration file (#179)

* When the repository is using the tool configuration file instead of UI patterns, the tool will analyse with that file (only for ESLint for now)

* We're now comparing the name of the tool instead of the shortName when running the analysis. This was needed because the call to the repository tools is returning the tool name rather than the shortName. The logic is the same.

* When we call the method to run the tools, if the user is not using a tool configuration file (so it's relying on the local tool configuration on tools-configs), we still check if there's a config file as before.

fix: fix Lizard analysis run and configuration creation CF-1999 (#178)

* fix: fix Lizard runner

* fix: refactor setup and fix Lizard remote init

* remove commented code

* fix copilot comments

* fix build errors

* fix config creation when parameters are not set

* fix Codacy issues

* fix indentation

bump: adds new semgrep rules (#177)

bump: go version (#176)

fix: not recommended patterns are now included in semgrep config CF-1…

…809 (#175)

* fix: not recommended patterns are now included in semgrep config CF-1809

* fix: semgrep rules updated CF-1809

fix toolname comparison during the analysis (#172)

* in analyse.go we now compare the tool name with the shortName (i.e. pmd 7.16.0 should be pmd-7 instead of pmd, which is version 6)

* we now translate the name of pmd according to the tool, the same as eslint: pmd 7.16.0 should be called as pmd-7 and pmd 6.55.0 should be called pmd

feature: Upload sourceId when available from SARIF CF-1813 (#173)

* feature: Upload sourceId when available from SARIF CF-1813

Note that this will upload it for all the tools and affect the
UUID generation, thus marking current issues as fixed/new
To have this feature only for some tools this is not enough

* feature: Only send sourceId for Trivy CF-1813

This will avoid messing with the results from other tools and
respectes on how codacy cloud and the CLI v1 handles it.

The downside is that will be a bit error prone when adding other tools
and if forget to add it, less results will be added on Codacy,
but for now it is an acceptable compromise

feature: adds trivy new patterns, high and critical, config mappings …

…CF-1860 (#171)

feature: trivy will now run with --detection-priority comprehensive C…

…F-1835 (#168)

fix: listing tools and patterns should allow disabled ones too (#170)

* fix: listing tools and patterns should allow disabled ones too

* bumplizard and trivy versions on codacy.yaml