feat: Implement no-exclusive-tests rule

[NoyanSeckin]

This rule prevents the usage of .skip and .only in tests.
(If approved, I can write the test cases for the rule)

[CLAassistant]

All committers have signed the CLA.

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[MikeMcC399]

@NoyanSeckin

I'm currently proposing some updates to this repo and I noticed your PR. I suggest instead of creating a new rule for eslint-plugin-cypress, use rules from eslint-plugin-mocha.

See the existing rules from eslint-plugin-mocha:

• no-exclusive-tests which covers the use of .only
• no-skipped-tests which covers the use of .skip

You can see an example of how eslint-plugin-cypress and eslint-plugin-mocha are combined In the cypress-io/cypress-example-kitchensink repo.

[MikeMcC399]

• This PR also overlaps the pending PR feat(rule): add no-focused-tests rule #82

[MikeMcC399]

@NoyanSeckin

Thanks for the suggestion in your PR! I'm going to close it now for several reasons:

• It overlaps with PR feat(rule): add no-focused-tests rule #82
• It intersects with the rules from eslint-plugin-mocha however it does not separate .only from .skip
• PR docs: add mocha instructions to readme #181 proposes to document how to achieve the goals with no changes to the plugin, so this PR then becomes unnecessary if users follow the suggested instructions for the README file.

I understand that the PR was not complete when you submitted it because you were looking for feedback. Because the PR is incomplete it also fails linting.