fix(no-node-access): false positives with props.children

[sjarva]

Checks

• I have read the contributing guidelines.
• If some rule is added/updated/removed, I've regenerated the rules list (npm run generate:rules-list)
• If some rule meta info is changed, I've regenerated the plugin shared configs (npm run generate:configs)

Changes

• checks if the node accessing property (e.g. children, firstChild or previousSibling) is called by props, so if there's a props.children, props.firstChild or props.previousSibling, then that code won't be reported as an error

Context

Closes #386 (at least the most common case, not all of the examples given in that issue).
This PR does not close/fix the deconstructed props case (mentioned by @Belco90 in #386):

function ComponentB({ children }) {
  // this should NOT be reported
  if (children) {
    // ...
  }

  // this should NOT be reported
  return <div>{children}</div>
}

But I am happy to make another PR about this case too (I just haven't figured out how to identify with AST).

P.S. If you feel that this PR is following the rules of Hactoberfest and this gets merged, it would be wonderful if this PR would be tagged with a hacktoberfest-accepted tag/label. Thanks!

[Belco90]

Just a small change in the docs and will be ready to merge.

[github-actions]

🎉 This PR is included in version 5.7.2 🎉

The release is available on:

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

Your semantic-release bot 📦🚀