Wrong message for anonymous functions

Consider the following scenario:

```ts
const Component = observer(function (props: IProps)) { /* Note that this is, in fact, an anonymous function */
const { useHook } = props;
const { myState } = useHook(); /* A hook cannot be used inside of another function */
return

const WrappedComponent = function() {
const [state, setState] = React.useState();
React.useEffect((
expensiveState.lazyImport().then(s => setState(s));
), []);

const Wrapper = React.useCallback(() => state ? /> : , [state])
return
}

ReactDOM.render(, ...)
```

It is in fact a wrong function React component declaration, as React component functions [must be named](https://github.com/facebook/react/blob/51947a14bb24bd151f76f6fc0acdbbc404de13f7/packages/eslint-plugin-react-hooks/src/RulesOfHooks.js#L48). However, I'm arguing that we should provide a meaningful and relevant error message, [analogous to the eslint plugin's](https://github.com/facebook/react/blob/51947a14bb24bd151f76f6fc0acdbbc404de13f7/packages/eslint-plugin-react-hooks/src/RulesOfHooks.js#L479).

Locate the TSLint rule that reports invalid React Hook usage and reproduce the anonymous-function example from the issue. Compare its diagnostic with the linked React ESLint rule, then verify that the reported message identifies the anonymous function and explains the invalid component declaration.

Written by the indexing model from the issue text.