text: Title: Investigate removing `prisma()` prefix from model-based queries
  Body: ## Problem
  
  <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
  
  We currently require that query methods called from model classes must first call `.prisma()`, e.g.
  
  ```py
  user = User.prisma().find_first(where={'name': 'Robert'})
  ```
  
  This was implemented this way to avoid any naming conflicts between fields and query methods. However, some people do not like that you have to call `.prisma()` first, we should look into changing this.
  
  ## Suggested solution
  
  <!-- A clear and concise description of what you want to happen. -->
  
  It *might* be possible to remove this and support directly querying, e.g. 
  
  ```py
  user = User.find_first(where={'name': 'Robert'})
  ```
  
  The only concern I have with this is that fields could be defined with the same name as a query method, this might not matter but if it does I do not want to have to disallow using fields with the same name.