chore: ✨ add initial configuration files for various tools and linters

[Anselmoo]

All PR-Submissions:

---

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open
  Pull Requests for the same
  update/change?

New ✨✨ Feature-Submissions:

---

• Does your submission pass tests?
• Have you lint your code locally prior to submission? Fixed:
• This PR is for a new feature, not a bug fix.

Changes to ⚙️ Core-Features:

---

• Have you added an explanation of what your changes do and why you'd like
  us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully run tests with your changes locally?

Summary by Sourcery

Add initial configuration files for Trunk and various linters and tools to set up project standards and automation.

Build:

• Add initial configuration files for Trunk, including trunk.yaml for managing plugins, runtimes, and linters.

Chores:

• Include configuration files for various linters and tools such as svgo, yamllint, ruff, hadolint, isort, markdownlint, and shellcheck.

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
.trunk/.gitignore	Unsupported file format
.trunk/configs/.hadolint.yaml	Unsupported file format
.trunk/configs/.isort.cfg	Unsupported file format
.trunk/configs/.markdownlint.yaml	Unsupported file format
.trunk/configs/.shellcheckrc	Unsupported file format
.trunk/configs/.yamllint.yaml	Unsupported file format
.trunk/configs/ruff.toml	Unsupported file format
.trunk/configs/svgo.config.js	0% smaller
.trunk/trunk.yaml	Unsupported file format

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR introduces initial configuration files for various development tools and linters using Trunk as the primary configuration management system. The implementation focuses on setting up a comprehensive set of linting and code quality tools with specific configurations for Python, JavaScript, Docker, Markdown, and shell scripts.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Set up Trunk as the main tool orchestrator with specific runtime and plugin configurations	Configured three runtime environments: Go 1.21.0, Node 18.20.5, and Python 3.10.8 Enabled multiple linters including black, pylint, ruff, prettier, and others Set up four trunk actions for announcing, pre-push checks, pre-commit formatting, and upgrade notifications	.trunk/trunk.yaml
Added specific linter configurations for various tools	Configured SVGO for SVG optimization with specific plugin parameters Set up YAML linting rules with custom quoted-string handling Created Ruff configuration with selected rule sets B, D3, E, F and ignored E501 Added Hadolint configuration to ignore specific shell source-related rules Configured isort to use black profile for compatibility Set up Markdownlint to be Prettier-friendly by extending prettier style	.trunk/configs/svgo.config.js .trunk/configs/.yamllint.yaml .trunk/configs/ruff.toml .trunk/configs/.hadolint.yaml .trunk/configs/.isort.cfg .trunk/configs/.markdownlint.yaml .trunk/configs/.shellcheckrc

---

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.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a 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. You can also use
  this command to specify where the summary should be inserted.

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.

[sourcery-ai]

Hey @Anselmoo - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider consolidating Python linting tools - having ruff, pylint, and black might be redundant. Ruff can handle most of pylint's checks with better performance.
• Consider adding documentation explaining the chosen tools and their versions to help future maintainers understand the decisions made.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

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.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (ee4ced3) to head (8781531).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1746   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           45        45           
  Lines         4520      4520           
=========================================
  Hits          4520      4520           

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.