Feat/align vcs pull request

[Jakub-Vacek]

This PR aligns vcs/pull-request with our conventions

Description

Motivation and Context

Types of changes

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

Checklist:

• [x] I have read the CONTRIBUTING document.
• [x] I haven't repeated the code. (DRY)
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.

[Jakub-Vacek]

Not sure about version raising, I agree it should be more than patch.

I will open separate PR for eslint. We should probably ignore anything generated (types, recordings, snapshots).

[Jakub-Vacek]

@freaz can I merge this? :)

[freaz]

Go for it.