Add "omitRouter" option

[blackarctic]

This allows for the following configuration:

Currently, my team is running into this situation where Router is provided at a higher point in the architecture and we want to use connected-react-router with our Redux store, but we need connected-react-router to use the Router instance that is higher up the tree instead of providing its own.

This option is added as opt-in only and should not affect any existing usage.

[blackarctic]

@supasate Anything I can do to help this along?

[blackarctic]

Until this is merged, I have a fork of this package up at https://www.npmjs.com/package/@blackarctic/connected-react-router

[blackarctic]

Bump

[supasate]

@blackarctic. Sorry for delayed response. Is your higher-level Router a React Router? If no, it would be out of scope of this package that intends for using with React Router. If yes, I would like to understand a bit more why you can't use ConnectedRouter instead of that React Router.

[blackarctic]

We are using Webpack 5 module federation. Thus the React Router is in the host application but each app is using its own Redux store with its own connected-react-router instance.

[supasate]

That sounds good to me. Would you mind adding a comment telling the use case of this option? So, other people can understand its purpose.

[blackarctic]

Sure. Preference on where?

[supasate]

LGTM. Thanks for your contribution!