feat: reverting contribution guide as it was wrongly pushed by bot

[emilianozublena]

…ll also help to fire the build process for the first public release

Description

It reverts back the contribution guide as it was recently introduced and updated.

Motivation and context

The change was a mistake when implementing the build process. We're reverting to the version we actually want and we're also marking as a feat so the release process is fired

How has this been tested?

No need for tests, it's only an MD

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

Go over all the following points, and put an x in all the boxes that apply.

Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.

• I have read the CONTRIBUTING document.
• My pull request addresses exactly one patch/feature.
• I have created a branch for this patch/feature.
• Each individual commit in the pull request is meaningful.
• I have added tests to cover my changes.
• If my change requires a change to the documentation, I have updated it accordingly.

If you're unsure about any of these, don't hesitate to ask. We're here to help!

[derberg]

you might want to change prefix of pr title to docs: or chore: otherwise minor release will be triggered

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[emilianozublena]

/rtm

[asyncapi-bot]

🎉 This PR is included in version 0.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀