Consider integrating settings and features into redux store #865
Description
Depends on #161
Instead of having dedicated contexts for features and settings in the ShlinkWebComponent, it might simplify things to move those to the redux store.
It would reduce the number of nested providers in tests, and also allow redux actions have access to settings and enabled features, without having to get them passed as argument.
The exception would be the settings component, which should not depend on the redux store. We should keep a dedicated settings context there.