Adopt Conventional Commits specification

[fra98]

Description

This PR adds new labels to better classify PRs and commits, adopting Conventional Commits specification.

In particular:

• commits should follow Conventional Commits. In particular, they should contain a <type> as prefix:
  • feat: 🚀 New Features
  • fix: 🐛 Bug Fixes
  • refactor: 🧹 Code Refactoring
  • docs: 📝 Documentation
  • style: 💄Code Style
  • perf: 🐎 Performance Improvement
  • test: ✅ Tests
  • chore: 🚚 Dependencies Management
  • build: 📦 Builds Management
  • ci: 👷 CI/CD
  • revert: ⏪ Reverts Previous Changes
• a label corresponding to the commit type should be added to PRs
• the automatic release notes generator will group PRs based on their commit type.

Note: the convention is adopted for releases > v1.0.0-rc.3

[adamjensenbot]

Hi @fra98. Thanks for your PR!

I am @adamjensenbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

• /rebase: Rebase this PR onto the master branch (You can add the option test=true to launch the tests
  when the rebase operation is completed)
• /merge: Merge this PR into the master branch
• /build Build Liqo components
• /test Launch the E2E and Unit tests
• /hold, /unhold Add/remove the hold label to prevent merging with /merge

Make sure this PR appears in the liqo changelog, adding one of the following labels:

• kind/breaking: 💥 Breaking Change
• kind/feature: 🚀 New Feature
• kind/bug: 🐛 Bug Fix
• kind/cleanup: 🧹 Code Refactoring
• kind/docs: 📝 Documentation

[fra98]

/hold until RC3