fix(react): track owners separately, mutate updaters with dispatcher

[CodyJasonBennett]

Fixes #125
Fixes #135
Fixes #70

This PR tracks ReactCurrentOwner separately from ReactCurrentDispatcher since the former is not guaranteed to be populated when ReactCurrentDispatcher is mutated. This is very evident from #125, and you can verify by running against a production build of React. Annoyingly, this behavior is different than that of a development build of React.

Additionally, signals' updaters are mutated on subsequent runs since there are multiple dispatchers during the lifecycle of a component, and holding on to a stale dispatcher can break the re-rendering mechanism (it wouldn't do anything).

Note: The relevant dispatcher states are invalid, mount, update, re-render -- invalid and re-render are skipped by isInvalidHookAccessor and lock, respectively. These are unique per reconciler, so #115 would have two pairs of mount and update dispatchers.

The changes in this PR originally came from tweaking with v1 JS output, which you can find in this gist. This is runnable if you want to copy/paste it into a Codesandbox, although ensure you're using the old JSX transform (React.createElement) if possible for the moment.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e3ead4a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[netlify]

✅ Deploy Preview for preact-signals-demo ready!

Name	Link
🔨 Latest commit	e3ead4a
🔍 Latest deploy log	https://app.netlify.com/sites/preact-signals-demo/deploys/632157c85d0c350008e6105b
😎 Deploy Preview	https://deploy-preview-130--preact-signals-demo.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[marvinhagemeister]

This looks great! Let's add one or few test cases that ensure that we don't regress on this in the future 👍

[CodyJasonBennett]

Would it be fine to settle for cases that cover the linked issues (doesn't crash in production, will consistently re-render in both production/strict-mode) or would you prefer to re-run the test suite (IDK how you'd sanely configure a testing matrix or mock/clear dependencies here)?

I'll commit the first in a moment as a baseline.

[marvinhagemeister]

Would it be fine to settle for cases that cover the linked issues

Sounds good enough to me 👍

Instead of mocking dependencies we could add a new alias to something like react-production that points to the production build. I'm good with merging it as is and we can always PR more on top later. What do you think?

[marvinhagemeister]

This is great! Thank you for your PR 🙌

[CodyJasonBennett]

We'll have to trust Netlify CI in lieu of a controlled production environment.