Integrate brisk reconciler core

[bryphe]

WIP: Replace reason-reactify with brisk-core

This change:

• Migrates our primitives to use the nativeComponent from brisk
• Migrates our components to the brisk component model
• Migrates our rendering logic to get the pending updates from brisk
• Migrates example

Remaining work:

• Finish Hello.re migration
• Get fix for useState in nested tree ([Test case] State update in subtree not being picked up briskml/brisk#31)
• Integrate useEffect implementation
• Implement animation primitive w/ new useEffect
• Hook up key handling in Calculator w/ useEffect
• Find way to detect changes (so we can implement uiDirty primitive and only render when an update is needed)
• Replace link: resolution with an NPM package for brisk-core
• Update esy.lock w/ dependency update
• Fix issue using Hooks.effect with condition OnMount

[wokalski]

I'd like to bring this to brisk-reconciler if possible. RemoteAction allows for just one subscriber.

[bryphe]

@wokalski , please feel free to bring it over 👍 (It had lived in reason-reactify before, anyway).

[wokalski]

Admittedly this is problematic about this API if you don't work with abstract types.

[bryphe]

Definitely. We'll likely revisit the decision to use class nodes or experiment / profile some alternate approaches.

[wokalski]

https://github.com/briskml/brisk-reconciler you can use this repo now!

[bryphe]

Excellent, thanks @wokalski ! Just waiting on CI but I think this is almost ready 🎉

Are you planning on publishing an NPM package, too?

[wokalski]

@bryphe if it’s not problematic for others I’d rather not just yet. I would like to rename a few types which might are technically breaking changes. Also, there might be further changes to the Hooks api (I.e. maybe you’ll return hooks from render). But when we have the ppx and the naming is ok, I’ll start publishing to npm.