Async ORM mutations and queries

[Archmonger]

Description

fix https://github.com/reactive-python/reactpy-django/issues/135

• Disable thread_sensitive where it's not needed
• Perform queries and mutations using async
  • use_query now supports async functions.
  • use_mutation now supports async functions.
  • django_idom.types.QueryOptions.thread_sensitive option to customize how sync queries are executed.
  • django_idom.hooks.use_mutation now accepts django_idom.types.MutationOptions option to customize how mutations are executed.
• Use Python's arg/kwarg handlers to properly interpret and differentiate between kwarg and args. This allow things such as query=my_function to be properly handled.
• The mutate argument on django_idom.hooks.use_mutation has been renamed to mutation.
• Add tests for our database routing feature
• Reduce runtime for tests from ~181 seconds to ~11 seconds by only starting the Django server once
• Fix bug where ReactPy utilizes Django's default cache timeout, which can prematurely expire our cache entries.

Checklist:

Please update this checklist as you complete each item:

• [x] Tests have been included for all bug fixes or added functionality.
• [x] The changelog has been updated with any significant changes, if necessary.
• [x] GitHub Issues which may be closed by this PR have been linked.

[Archmonger]

@rmorshea I'm seeing some weird behavior that might indicate a bug with async use_effect hooks.

Let me know when you have time for me to demo.

[rmorshea]

I'll have time in an hour.

[Archmonger]

Ops forgot to add async mutation support...

EDIT: Past me apparently already semi-developed it, but I'm not sure what direction to take for a thread_sensitive parameter for mutations. I think we might need to create a MutationOptions data type.

[Archmonger]

@rmorshea

Regarding a thread_sensitive parameter for mutations, which approach do we want to take?

1. Create a MutationOptions data type with a thread_senstive parameter.
2. Assume all sync mutations are thread_sensitive
   • If we do this, we should probably make the same assumption for our use_query hook
3. Add a thread_sensitive=... kwarg directly to use_mutation
   • This might feel weird, since it ends up being a different API than use_query

[Archmonger]

I opted for use_mutation with MutationOptions since I think it's the only API that doesn't feel mismatched when comparing to use_query with QueryOptions.

We should re-evaluate when merging these hooks into core.

In the future, I'd like these settings to either be kwargs or a TypeDict (assuming editors start having TypeDict auto completion)

[Archmonger]

This PR is ready for review.

I did a tabletop self-review and cleaned up a couple things.

[rmorshea]

Will try to find time. Going to be quite busy the next two weeks.

[Archmonger]

I played around with the test to get things running faster and more reliably.

[Archmonger]

@rmorshea Can we schedule a review for this one?