[Consistency/Scanners] SCB scanners use different versioning system

Working on the consistency of all scanner files, it was noticed that our own scanners (SCB scanners), that is test-scan, git-repo-scanner and zap-advanced, use a different versioning scheme which is linked to the scb releases. This leads to an inconsistent and potentially confusing use of Chart.Version vs. Chart.AppVersion in the scan-type.yaml file:

Git-Repo-Scanner (SCB) - Chart.Version (linked to SCB release):

 - name: git-repo-scanner
       image: "{{ .Values.scanner.image.repository }}:{{ .Values.scanner.image.tag | default .Chart.Version }}"

Nmap (Extern) - Chart.AppVersion (linked to current nmap release):

  - name: nmap
        image: "{{ .Values.scanner.image.repository }}:{{ .Values.scanner.image.tag | default .Chart.AppVersion }}"

Although this is a minor issue, it should probably kept in mind when new internally maintained scanners are added to the SCB.

Also affects scanner.image.tag in values.yaml.

The following scanners are affected:

• git-repo-scanner
• screenshooter
• test-scan
• zap-advanced

Start by locating the affected scanner chart files, especially scan-type.yaml and values.yaml, and compare how Chart.Version, Chart.AppVersion, and scanner.image.tag are used for zap-advanced and the other listed SCB scanners. Confirm the intended versioning convention with the project maintainers, then update the affected references consistently and verify the rendered scanner image tags.