Improve CONTRIBUTING

[Freymaurer]

• Relax contribution restrictions: Requires specific commit syntax => increased entry barrier
• Add .editorconfig: CONTRIBUTING.md says 4 spaces and format with fantomas. But the repository does not have any fantomas settings (e.g. .editorconfig). So this could create different outcomes per person. For example for me fantomas has a default of 2 spaces.

[shayanhabibi]

With regards to the commit syntax, as mentioned in the docs:

Ensure all commits and merges into the main branch use conventional commits.

Other commits will be excluded from the release notes, and from consideration for versioning.

You can choose to squash pulls into a conventional commit if this is easier.

Try to keep commits for different projects separate to each other. This will allow your commit messages, and the subsequent release notes to be more informative.

If you can't decide between the type of a commit, always default to the higher one (ie, if you have a squashed commit for a fix and feature, make the type a feature).

We can include non conventional commits in the changelog. The idea behind using this setting was to allow 'wip' like commits to be ignored in the changelog in favour of the final conventionalcommit message.

This only applies for the sake of versioning. You can commit in any manner in any other circumstance, and then make the commit that triggers the versioning using conventional commits.

Using conventional commits is better, in that the changelog will link directly to the commit with the correct diffs.

Tldr:
Theres no penalty to committing in any other style except for the implications with automatic versioning

[Freymaurer]

I added a .editorconfig for fantomas.

Could you add some examples for the commit syntax? I know its more or less:

feat: Add new methods

Breaking
feat!: Add new methods

But do we use scopes? From the RELEASE_NOTES i would assume so?