text: Title: Raise a warning on multiple rapid connections / disconnections
  Body: ## Problem
  
  <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
  
  Currently an easy mistake to make is to use the client's context manager feature on every database query e.g.
  
  ```py
  async with client:
      user = await User.prisma().find_unique(
          where={
              'id' user_id,
          },
      )
  ```
  
  This is a mistake when used in anything other than a small seed script as it will create a connection pool and connect to the database only to close the pool and disconnect immediately afterwards. This is very inefficient and should only be done once per application runtime.
  
  ## Suggested solution
  
  <!-- A clear and concise description of what you want to happen. -->
  
  I believe this mistake is easy to make as the initial `connect()` must be called explicitly by the user and sometimes it is not very obvious where to do this. (#103 will solve this).
  
  We should update the documentation for connecting with the context manager with a big warning saying not to use this repeatedly in actual applications.
  
  We should also consider raising a warning if many calls to `connect()` and `disconnect()` are  encountered. There should also be an easy way to disable these checks, maybe a new client parameter?
  
  ## Additional context
  
  <!-- Add any other context or screenshots about the feature request here. -->
  
  Encountered this pattern while reading through open source code:
  
  https://github.com/shydiscord/shy-dashboard/blob/f708c3a70d9e3aaa60f6bae693bf649d27883ea0/shy-dashboard/server/blueprints/api.py