New rule: react-no-throw-in-lifecycle

[adidahiya]

some good advice from @crazytoucan (abridged):

Sometimes your whole app crashes, because of a single React component that threw: maybe render() tried to map an array that was undefined, or WillMount() tried to talk to a service that threw internally
...
there’s ultimately no reliable way to recover from a crashed component as a library or utility.
...
Simply put, you should never throw inside your React lifecycle methods. If this means a little bit of extra defensive programming, I think component resilience is a worthwhile cost. Don’t litter code with unnecessary invariant checks ...

We should look into a lint rule that can enforce this.

[OzairP]

Not needed in React 16 due to Error Boundary

[adidahiya]

Closing due to old age and deprecation timeline #210