Bug: eslint-plugin-react-hooks doesn't report conditional typescript "?." hooks

**React plugin version:** eslint-plugin-react: "^7.19.0" typescript: 4.0+ (must include ?. operator) ## Steps To Reproduce ```tsx // Just a demonstration example, obviously this is not ideal use of classes class Dog { public useDogWoof() { useEffect(() => { console.log("woof") }]) } } const DogWoof = ({dog}: {dog?: Dog) => { dog?.useDogWoof() // Should print conditional hook error return ( // ) } ``` ## The current behavior Typescript has the new 4.0 operator `?.` in case an object is undefined. But, this doesn't quite work along with hooks, as when the object is undefined, the hook is not called, thus the React Renderer complains that the amount of hooks is not the same or even worse untraceable type errors that I had. `eslint-plugin-react-hooks` is expected to be able to guard against that as well to prevent nasty errors with this new typescript operator. ## The expected behavior Currently, `eslint-plugin-react-hooks` doesn't take care of the typescript operator and thinks that nothing's wrong with using along one with a react hook.