feat: add no-chained-get rule

[duranbe]

This PR creates a new rule to disallow the usage of cy.get().get() as .get() is often misused as it is starting search from the document and the previously selected element.

• Closes Add a new rule to prevent chaining get queries #134

[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]

Possibly this should link to [cy.get()](https://on.cypress.io/api/get) (cy.get())

In the section https://docs.cypress.io/api/commands/get#Get-vs-Find it shows an example valid use of cy.get('#comparison').get('div')

cy.get('#comparison')
  .get('div')
  // finds the div.test-title outside the #comparison
  // and the div.feature inside
  .should('have.class', 'test-title')
  .and('have.class', 'feature')
cy.get('#comparison')
  .find('div')
  // the search is limited to the tree at #comparison element
  // so it finds div.feature only
  .should('have.length', 1)
  .and('have.class', 'feature')

[MikeMcC399]

@duranbe

I suggest that you either remove the heading ## Further Reading if there is no content for this section, or you link to the documentation page

[jennifer-shehane]

@duranbe Do you have time to address feedback here?

[duranbe]

Hey - sorry missed this ! Thanks for the feedbacks, addressing them

[MikeMcC399]

@duranbe

Thank you for resolving the comments!

[jennifer-shehane]

🎉 This PR is included in version 4.3.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀