Updates for unsafe lifecycles -> Package will break in React 17.0

In React 16.3, aliases were introduced for unsafe lifecycles:

- UNSAFE_componentWillMount
- UNSAFE_componentWillReceiveProps
- UNSAFE_componentWillUpdate

In the most recent version of React (16.9.*), console warnings highlight that starting with React 17.0, if you are not using the UNSAFE aliases, the component will not work.


Would you be able to publish a new package with the unsafe aliases in place?

```
cd your_project
npx react-codemod rename-unsafe-lifecycles
```

More information can be found here: https://reactjs.org/blog/2018/03/27/update-on-async-rendering.html

Use the React 17 lifecycle guidance and the `npx react-codemod rename-unsafe-lifecycles` command as starting references, then locate the package's lifecycle methods. Done means the package uses the UNSAFE_ lifecycle aliases and avoids the React 17 lifecycle compatibility warning.

Written by the indexing model from the issue text.