[CI/Build] Pipeline Checks

[AhmedSeemalK]

This pull request introduces a comprehensive set of GitHub Actions workflows to automate code quality, security, and dependency checks. These workflows cover linting, static analysis, vulnerability scanning, and supply-chain security, providing a robust CI foundation for the repository.

The most important changes are:

Security and Static Analysis Workflows:

• Added .github/workflows/bandit.yml to run Bandit for Python security analysis, including scheduled and PR-based runs, and uploads SARIF results.
• Added .github/workflows/checkov.yml to run Checkov for Kubernetes, GitHub Actions, and secrets scanning, with results uploaded in SARIF format.
• Added .github/workflows/trivy.yml to run Trivy for vulnerability, secret, license, and misconfiguration scanning, with separate SARIF uploads for each scan type.
• Added .github/workflows/shellcheck.yml to lint shell scripts using ShellCheck, with custom logic to distinguish entry points and helpers.
• Added .github/workflows/ansible-lint.yml to lint Ansible roles and playbooks using ansible-lint.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.