Adapt pipeline_definition to include SAST linting logs in OCM descriptor

[aaronfern]

What this PR does / why we need it:
The PR does the following

• changes pipeline_definitions to include SAST linting logs in OCM descriptor.
• Fixes some security vulnerabilities
• Updated the check make command to run sast

Which issue(s) this PR fixes:
Fixes #331

Special notes for your reviewer:

Release note:

NONE

[gardener-robot-ci-3]

This PR proposes changes that would break the pipeline definition:

autoscaler-sast-ocm: Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/concourse/replicator.py", line 141, in render
    definition_descriptor = self._render(definition_descriptor)
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/concourse/replicator.py", line 185, in _render
    'definition': factory.create_pipeline_definition(),
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/concourse/factory.py", line 88, in create_pipeline_definition
    self._apply_traits(variant)
  File "/usr/lib/python3.12/site-packages/concourse/factory.py", line 177, in _apply_traits
    transformer.process_pipeline_args(pipeline_def)
  File "/usr/lib/python3.12/site-packages/concourse/model/traits/release.py", line 520, in process_pipeline_args
    raise ValueError(textwrap.dedent(f'''\
ValueError: asset=BuildstepLogAsset(ocm_labels=[{'name': 'gardener.cloud/purposes', 'value': ['lint', 'sast', 'gosec']}, {'name': 'gardener.cloud/comment', 'value': 'we use gosec (linter) for SAST scans\nsee: https://github.com/securego/gosec\n'}], type='build-step-log', name='check-build-step-log', step_name='check', artefact_type='application/data', artefact_extra_id={}, purposes=['lint', 'sast', 'gosec'], comment='we use gosec (linter) for SAST scans\nsee: https://github.com/securego/gosec\n', upload_as_github_asset=True, github_asset_name=None)'s step_name refers to an absent build-step. If the step in question is
declared branch-specifically, i.e. via `branch.cfg`, and the current branch is
going to be merged with a branch declaring the pipeline step, this error can be
safely ignored, iff the branch is transient only (not used for release).

[gardener-robot]

@unmarshall You have pull request review open invite, please check

[ashwani2k]

Looks good to me. I ran the report and with GOSEC ignore annotation set the Issues reported were zero.

[gardener-robot-ci-2]

The pipeline-definition has been fixed.

[ashwani2k]

Looks good to me.