limit no-node-access errors reported

[Belco90]

Originated by #331. I don't think no-node-access should report DOM elements queried from document since we can't detect properly if being used for a test because of Aggressive Reporting.

In the rule doc it says this case is invalid:

// If is not importing a testing-library package

document.getElementById('submit-btn').closest('button');

But we can't actually know this for the reason mentioned before.

[Belco90]

Additionally, seems this rule is too aggressive and could trigger tons of false positives outside test files, I think it's necessary to avoid Aggressive Reporting on this rule and make it reporting errors only if @testing-library/* or custom module set through Shared Settings imported.

This would make the previously mentioned invalid case doable. It could still cause some false negatives and silence some errors here and there, but I think it's necessary given how aggressive this rule is.

[github-actions]

🎉 This issue has been resolved in version 4.0.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀