feat: no-implied-descendent in /react ruleset

[codejedi365]

Feature Request

Create a rule that errors when a ReactSelector() parameter uses an html entity as a descendent selector without specifying it as a direct descendent with >.

Problem & Goal

testcafe-react-selectors warns about using ReactSelector() with a parameter of a 'ReactComponent div' when the div will only match direct children of the ReactComponent and not all the children of the subcomponent.

// Example html
<TodoApp className="todo-app">
    <TodoInput />
    <TodoList>
        <TodoItem priority="High" key="HighPriority">Item 1</TodoItem>
        <TodoItem priority="Low" key="LowPriority">Item 2</TodoItem>
    </TodoList>

    <div className="items-count">Items count: <span>{this.state.itemCount}</span></div>
</TodoApp>

// Extraction code
import { ReactSelector } from 'testcafe-react-selectors';

const TodoList         = ReactSelector('TodoApp TodoList');
const itemsCountStatus = ReactSelector('TodoApp div');

// itemsCountStatus == Selector('.todo-app > div')

The goal here is to enforce an explicit use of the immediate descendent css selector > to ensure the limitation of the library is not overlooked.

Expected behavior