feat: added codespell

[mfranzke]

Proposed changes

Types of changes

• Bugfix (non-breaking change that fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (improvements to existing components or architectural decisions)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Further comments

[github-actions]

🔭🐙🐈 Test this branch here: https://db-ux-design-system.github.io/core-web/review/feat-added-codespell

[nmerget]

We should find a npm package which does the same to lint it like markdownlint etc.

If we just add it in the pipeline we wouldn't have any possibility to check issues locally

[mfranzke]

We should find a npm package which does the same to lint it like markdownlint etc.

If we just add it in the pipeline we wouldn't have any possibility to check issues locally

I'm not totally sure about this – I did a quick research, but haven't found anything as a node module. I'll follow up on this, but maybe it's something that only the pipeline could tell us finally.

[mfranzke]

We should find a npm package which does the same to lint it like markdownlint etc.
If we just add it in the pipeline we wouldn't have any possibility to check issues locally

I'm not totally sure about this – I did a quick research, but haven't found anything as a node module. I'll follow up on this, but maybe it's something that only the pipeline could tell us finally.

"code-spell" instead of "codespell" does the trick …