Disable internal sast scanning tools in favor of gosec

.ci/pipeline_definitions

@@ -3,7 +3,7 @@
 # SPDX-License-Identifier: Apache-2.0
 
 gardener-extension-shoot-lakom-service:
-  templates: 
+  templates:
     helmcharts:
     - &shoot-lakom-service
       name: shoot-lakom-service
@@ -34,6 +34,13 @@ gardener-extension-shoot-lakom-service:
         attribute: image.tag
 
   base_definition:
+    repo:
+      source_labels:
+      - name: cloud.gardener.cnudie/dso/scanning-hints/source_analysis/v1
+        value:
+          policy: skip
+          comment: |
+            We use gosec for sast scanning, see attached log.
     traits:
       version:
         preprocess: 'inject-commit-hash'
@@ -112,6 +119,16 @@ gardener-extension-shoot-lakom-service:
           nextversion: 'bump_minor'
           next_version_callback: '.ci/prepare_release'
           release_callback: '.ci/prepare_release'
+          assets:
+          - type: build-step-log
+            step_name: verify
+            purposes:
+            - lint
+            - sast
+            - gosec
+            comment: |
+              We use gosec (linter) for SAST scans, see: https://github.com/securego/gosec.
+              Enabled by https://github.com/gardener/gardener-extension-shoot-lakom-service/pull/116
         slack:
           default_channel: 'internal_scp_workspace'
           channel_cfgs: