🚧 [Consistency] Ensuring file/code consistency for scanners #620

As a secureCodeBox developer and maintainer I would like to have consistency between all provided resources, especially scanners. This should speed up the development process, enable a consistent documentation and make maintenance simpler.

Consistency can be achieved manually by aligning all existing files manually, I think the best and most sustainable way would be to have tests (in the ci pipeline), that point out on inconsistent file and coding standards.

Files that should be considered for scanners:

• Chart.yaml (🚧 [Consistency] Make all Chart.yaml files follow the same template #685)
• values.yaml (🚧 [Consistency] Make all values.yaml files follow the same template #693)
• templates/cascading-rules.yaml (🚧 [Consistency] Make all cascading-rules.yaml files follow the same template #691)
• templates/scanner-name-parse-definition.yaml
• templates/scanner-name-scan-type.yaml (🚧 [Consistency] Make all scan-type.yaml files follow the same template #689)
• parser: All parsers should be tested for an empty / erroring result file (🚧 [Consistency] Test all parsers for handling of an empty result file #701)
• parser: All parsers should have the same output standard for findings (see Make Location a required field and ensure it is a valid URL #619)

Ensuring consistency in the future:

• Create template files and a make command to automatically create a new scanner directory with consistent files (🚧 [Consistency] Adding template files and a make command to create new scanners #684)
• Change documentation where necessary