chore: clean up configuration files and workflows

[TommyE123]

This pull request primarily updates configuration files related to CI workflows and linting tools. The changes focus on improving workflow triggers.

CI/CD Workflow Updates:

• .github/workflows/mega-linter.yml: Changed the MegaLinter workflow to trigger only on pull requests to main, rather than on every push, reducing unnecessary workflow runs.

Linting Configuration Improvements:

• .yamllint.yml: Disabled the document-start rule to allow YAML files without a --- at the start, increasing flexibility for YAML formatting.

Summary by Sourcery

Align CI and linting configuration by simplifying workflow triggers and normalizing YAML config headers.

Enhancements:

• Disable the yamllint document-start rule to allow YAML files without leading document separators.
• Remove leading YAML document header markers from various configuration and workflow files for consistency.

CI:

• Update MegaLinter GitHub Actions workflow to run only on pull requests targeting the main branch.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates CI workflows to only run MegaLinter on pull requests to main and cleans up various YAML-based configuration files by removing leading document markers and relaxing a yamllint rule for document-start markers.

Flow diagram for updated MegaLinter CI trigger configuration

flowchart TD
  Dev[Developer opens or updates PR]
  Event{PR base branch is main?}
  Event -- yes --> ML[MegaLinter workflow runs]
  Event -- no --> Skip[MegaLinter workflow not triggered]

Loading

File-Level Changes

Change	Details	Files
Adjust MegaLinter GitHub Actions workflow trigger to run only on pull requests to main.	Remove push trigger configuration from the MegaLinter workflow. Configure workflow to trigger on pull_request events targeting the main branch. Update workflow comments to reflect the new triggering behavior.	.github/workflows/mega-linter.yml
Relax YAML linting rules to allow files without YAML document-start markers and clean up superfluous document markers across configs.	Disable yamllint's document-start rule to permit YAML files without leading --- markers. Remove top-level --- document-start markers from YAML-based configuration files to align with the relaxed rule and simplify file headers.	.yamllint.yml .checkov.yml .github/ISSUE_TEMPLATE/issue.feature.yml .github/workflows/deploy-docker-image.yml .github/workflows/greetings.yml .github/workflows/lint-pr-title.yml .hadolint.yml .mega-linter.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[github-actions]

Thanks for opening this pull request! Be sure to follow the pull request template!

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ ACTION	actionlint	4		0	0	0.2s
✅ ACTION	zizmor	4	0	0	0	3.05s
✅ DOCKERFILE	hadolint	1		0	0	0.26s
✅ EDITORCONFIG	editorconfig-checker	42		0	0	0.09s
✅ JSON	jsonlint	2		0	0	0.42s
✅ JSON	prettier	2	0	0	0	0.22s
✅ JSON	v8r	2		0	0	1.45s
✅ MARKDOWN	markdownlint	2	0	0	0	0.61s
✅ MARKDOWN	markdown-table-formatter	2	0	0	0	0.14s
✅ REPOSITORY	betterleaks	yes		no	no	0.73s
✅ REPOSITORY	checkov	yes		no	no	29.23s
✅ REPOSITORY	devskim	yes		no	no	0.77s
✅ REPOSITORY	dustilock	yes		no	no	0.4s
✅ REPOSITORY	gitleaks	yes		no	no	0.25s
✅ REPOSITORY	git_diff	yes		no	no	0.01s
✅ REPOSITORY	grype	yes		no	no	54.21s
✅ REPOSITORY	kingfisher	yes		no	no	7.92s
✅ REPOSITORY	osv-scanner	yes		no	no	0.31s
✅ REPOSITORY	secretlint	yes		no	no	0.49s
✅ REPOSITORY	syft	yes		no	no	1.8s
✅ REPOSITORY	trivy	yes		no	no	11.83s
✅ REPOSITORY	trivy-sbom	yes		no	no	0.13s
✅ REPOSITORY	trufflehog	yes		no	no	2.8s
✅ YAML	prettier	10	0	0	0	0.61s
✅ YAML	v8r	10		0	0	4.2s
✅ YAML	yamllint	10		0	0	1.27s

See detailed reports in MegaLinter artifacts

Show us your support by starring ⭐ the repository