Improvement/hoc react functional modules

[Vadko]

Description

Solution in relevant pull request complements one of previous fixes related to the React functional components: #219

Related Issues

Fix that included in mentioned above PR resolves issue about cognitive complexity score redundancy when using React functional components with additional score for nested if else condition inside of functional component methods. It works as expected, but the problem comes up when we are wrapping our functional component with HOC - in my case it was memoization function which are often used inline - this leaded to same issue with redundant +1 score for nested conditions in methods.

For fixing that, I've decided to look for a parent node name with additionally considering if we are returning JSX element/fragment to properly check is that a functional component or not.

Tests

I added the following test in cognitive complexity rule tester:

 {
      code: `
      const Welcome = memo(() => {
        const handleSomething = () => {
          if (x) {} // +1
        }
        if (x) {} // +1
        return <h1>Hello, world</h1>;
      })`,
      parserOptions: { ecmaFeatures: { jsx: true } },
      options: [0],
      errors: [message(1, { line: 2 }), message(1, { line: 3 })],
    }

Test Suites: 34 passed, 34 total
Tests: 561 passed, 561 total
Snapshots: 0 total
Time: 6.116 s

[saberduck]

we did some improvements to cognitive complexity and JSX interaction, I think it's sufficient now.