Bug fix for corrupted hook state

[Archmonger]

Description

Due to some backends re-using threads across multiple requests, the hook stack could potentially become corrupted resulting in the following error: RuntimeError("Hook stack is in an invalid state")

Note to self, consider replacing _ThreadSafeQueue with janus in this PR.

Remaining TODOS

• Figure out why this change breaks the test suite
  • Perhaps it is related to weirdness with how async fixtures run on pytest?

Checklist

Please update this checklist as you complete each item:

• Tests have been developed for bug fixes or new functionality.
• The changelog has been updated, if necessary.
• Documentation has been updated, if necessary.
• GitHub Issues closed by this PR have been linked.

_{By submitting this pull request I agree that all contributions comply with this project's open source license(s).}

[Archmonger]

@JamesHutchison I split your ContextVar changes into this PR but it doesn't appear to work within the test suite. Running the test suite results in the following error: LookupError: <ContextVar name='_hook_state' at 0x000001AC3906CF90>

These changes do seem to work fine outside the test runner though - Are there any other changes I'm supposed to migrate from #1204 to get this working?

[JamesHutchison]

The issue is likely that the tests are missing a call to create_hook_state that occurs normally during the rendering loop. I did not run the reactpy tests against my code in the marathon coding week that I wrote most of this. You could probably just add an automatic test fixture.

I do not test reactpy code automatically so this doesn't show up in Heavy Resume.