Draft: 🐋 Add yaml-lint github action and add .editorconfig

[tzabbi]

Fixes #510

Summary

Add yaml-lint github action job and .editorconfig

Changes

• to have a standardized YAML code style, we implement YAML lint GitHub action
• to have some unified code rules through all files, we add a .editorconfig

Submitter checklist

• Add the correct emoji to the PR title
• Link the issue number, if any, to Fixes #
• Add summary and explain changes in the PR description
• Rebase branch to HEAD
• Squash changes into one signed, single commit ¹

Footnotes

1. See suggested commit format ↩

[amorey]

Let's ignore pnpm-lock.yaml and other generated yaml files because otherwise we'll be in constant contention with the code generators

[amorey]

Does it make sense to use a one-step yamllint action? I don't have any personal experience with them but here are some options:
https://github.com/marketplace/actions/yaml-lint
https://github.com/marketplace/actions/yamllint-github-action

[tzabbi]

I just used the example from the yaml lint documentation: https://yamllint.readthedocs.io/en/latest/integration.html#integration-with-github-actions

[amorey]

The current .editorconfig settings will contend with the gofmt tool that uses tabs instead of spaces. Considering that this is a multi-language monorepo does it make more sense to configure each language formatter separately?

[tzabbi]

I will fix everything after my vacation.

[tzabbi]

@amorey do you have some requirements for rust, go, ... files in regard of code syntax? I will add them to the .editorconfig. Same for the yaml linter, which files will be autogenerated?

[amorey]

@tzabbi Currently we're language-specific linters and vetters with their default setups (see ci.yml).