Fixed invariant issue by removing react from list of dependencies

This issue is in regards to issue https://github.com/STRML/react-router-component/issues/102

Citing similar issue from react-draggable github issue tracker:
- react-draggable issue: https://github.com/mzabriskie/react-draggable/issues/22
- react-draggable merge changes: https://github.com/mzabriskie/react-draggable/commit/d562500081cad766c117d2618bce9f16cb231251

Comment cited above states:
> This is due to react-draggable including react as a dependency [...]
> 
> The solution is to move react from dependencies to devDependencies. Ideally, it should be in peerDependencies, but older versions of npm don't support the property.

`make test-local` passed all tests.

Further testing within multiple environments were successful as well.

**react-router-component**
*0 failing 39 passing*
Routing :: renders
Routing :: passes props from location down to handler
Routing :: navigates to a different route
Routing :: navigates to a different route (w/o callback)
Routing :: handles "popstate" event
Routing :: navigates to a different route (replacing current history record)
Routing :: renders to NotFound if not match is found
Routing :: Navigation lifecycle callbacks :: calls onBeforeNaviation and onNavigation
Routing :: Link component :: navigates via .navigate(path) call
Routing :: Link component :: navigates via onClick event
Routing :: Link component :: navigates even if it is situated outside of the router context
Routing :: Link component :: doesn't navigate if the default is prevented
Routing :: CaptureClicks component :: navigates via onClick event
Routing :: CaptureClicks component :: doesn't navigate if the href has another host
Routing :: CaptureClicks component :: follows the link if the href has no matching route
Routing with async components :: renders async component
Routing with async components :: renders async component and navigates
Routing with async components :: cancels pending update on navigate
Routing with async components :: does not trigger async state load if type of the next component is the same
Nested routers :: navigates to a subroute
Nested routers :: navigates to a subroute (root case)
Nested routers :: CaptureClicks component :: navigates to a subroute via onClick event
Nested routers :: CaptureClicks component :: navigates to a subroute via onClick event (root case)
Contextual routers :: navigates to a subroute
Contextual routers :: navigates to a subroute (root case)
Contextual routers :: scopes router.navigate() to a current context
Contextual routers :: scopes Link to a current context
Contextual routers :: does not scope global Link to a current context
Multiple active routers :: renders
Multiple active routers :: navigates to a different route
Multiple active routers :: navigates to a different route (using another router)
Multiple active routers :: handles "popstate" event
Hash routing :: renders
Hash routing :: navigates to a different route (replacing current history record)
Hash routing :: navigates to a different route
Hash routing :: handles "haschange" event
Hash routing :: Link component :: navigates via .navigate(path) call
Hash routing :: Link component :: navigates via onClick event
Contextual Hash routers :: Link component :: does not scope globalHash Link to a current context