Disable Linting on branch master and releases

[palexster]

Description

We recently introduced a stricter linter on the Liqo code. The intention is to gradually improve the average quality and uniform the style of the repository.

Since we decided to have a gradual approach, this check is always broken on the main branch bringing a "broken window" effect on the repository status.

This PR drops the execution of such check on the main branch and releases, leaving it only for PRs.

How Has This Been Tested?

This PR introduces no functional changes to the code.

[adamjensenbot]

Hi @palexster. 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
• /merge: Merge this PR into the master branch
• /ok-to-test Enable testing for PRs with base on forks

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

[palexster]

/merge