[VO-221] feat: Add BarComponent v2

[cballevre]

The idea behind this PR is to expose the bar component via <BarComponent> so it can be integrated in the react-dom. The expected benefits are to be able to Provider from the app directly into the . This also make specific development of custom part more easy because it shares the same context.

The bar stay at the same place into the dom but appears into the React component tree with createPortal api.

Example of migration :

• https://github.com/cozy/cozy-drive/pull/2810
• https://github.com/cozy/cozy-settings/pull/652
• https://github.com/cozy/coachCO2/pull/382

Remaining work :

• Improve documentation

Future work :

• Remove old demo and use Storybook to make a new one
• Use css variable from cozy-ui to manage dark theme
• Remove enzyme

[cballevre]

I discovered a regression after migrating to Drive. I don't manage the application's custom stores, so certain functions no longer work in the custom components. I'm looking at how to mitigate the problem 😞

[cballevre]

I've reworked the redux part so that we can integrate the cozy-bar store into an application's store. I haven't found a way of merging two stores to avoid exposing the reducers and losing the advantage of middlewares. @Crash-- I'd like your opinion on this last commit 🙂

[cozy-bot]

:tada: This PR is included in version 11.0.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: