text: Title: Support disabling HTTP connection pooling
  Body: ## Problem
  
  <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
  
  Some frameworks (e.g. Flask Async) are incompatible with global asynchronous HTTP connection pooling as they spawn workers in separate threads with their own event loop. As the connection pool is tied to the event loop it was started in the aforementioned behaviour can lead to confusing event loop errors.
  
  This makes it impossible to use Prisma Client Python with such frameworks as the alternative solution (apart from monkeypatching) is to connect to the database separately on each worker thread however this has severe performance and database connection limit concerns.
  
  ## Suggested solution
  
  <!-- A clear and concise description of what you want to happen. -->
  
  We *could* support local HTTP connection pooling such that each event loop gets its own HTTP connection pool however I do not know how well this would work in practice:
  
  - Performance concerns with rapidly opening and closing a connection pool - would it be better to not use a connection pool?
  - Increased memory usage
  - Scalability concerns
  
  As such I think that the best solution (at least in the short term) is to add an option to disable HTTP connection pooling entirely while we figure out whether or not local HTTP connection pooling would be a viable solution.
  
  ```py
  client = Client(
      http={
          'use_pool': False,
      },
  )
  ```
  
  ## Additional context
  
  <!-- Add any other context or screenshots about the feature request here. -->
  
  See this discussion: https://github.com/RobertCraigie/prisma-client-py/issues/224#issuecomment-1034015273
  