Connect React context provider if it is created after a child using that context has been already hydrated

[luisherranz]

If a block that provides a React context is hydrated after a block child that uses that context, the context is not connected between the two.

That works correctly in React: https://codesandbox.io/s/romantic-mclean-fc26hm?file=/src/App.js

You can test it out by adding a setTimeout with a bigger value to the Interactive Parent block so it is hydrated after the Interactive Child block.

Related to #57.

[luisherranz]

Closed as we're not actively working on this experiment anymore and this works fine in the Directives Hydration.