text: Title: Mapped columns cannot be used with type safe raw queries
  Body: <!--
  Thanks for helping us improve Prisma Client Python! 🙏 Please follow the sections in the template and provide as much information as possible about your problem, e.g. by enabling additional logging output.
  
  See https://prisma-client-py.readthedocs.io/en/stable/reference/logging/ for how to enable additional logging output.
  -->
  
  ## Bug description
  
  <!-- A clear and concise description of what the bug is. -->
  
  If a column is mapped to a different name at the database level then pydantic will raise a ValidationError when attempting to construct the model object:
  
  ```prisma
  model User {
    id      String   @id @default(cuid())
    name    String   @map("username")
    email   String?  @unique
    posts   Post[]
    profile Profile?
  }
  ```
  ```py
  query = '''
      SELECT *
      FROM User
      WHERE User.id = ?
  '''
  found = await client.query_first(query, user.id, model=User)
  ```
  ```
  /private/tmp/tox/prisma-client-py/py39/lib/python3.9/site-packages/prisma/client.py:308: in query_first
      results = await self.query_raw(query, *args, model=model)
  /private/tmp/tox/prisma-client-py/py39/lib/python3.9/site-packages/prisma/client.py:338: in query_raw
      return [model.parse_obj(r) for r in result]
  /private/tmp/tox/prisma-client-py/py39/lib/python3.9/site-packages/prisma/client.py:338: in <listcomp>
      return [model.parse_obj(r) for r in result]
  pydantic/main.py:511: in pydantic.main.BaseModel.parse_obj
      ???
  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
  
  >   ???
  E   pydantic.error_wrappers.ValidationError: 1 validation error for User
  E   name
  E     field required (type=value_error.missing
  ```
  
  ## How to reproduce
  
  <!--
  Steps to reproduce the behavior:
  1. Go to '...'
  2. Change '....'
  3. Run '....'
  4. See error
  -->
  
  - Add the `@map` declaration to the test user model
  - Migrate the database (`prisma db push`)
  - Run `tox -e py39 -- -x tests/test_raw_queries.py::test_query_first_model`
  
  ## Expected behavior
  
  <!-- A clear and concise description of what you expected to happen. -->
  
  No errors should be raised, the column name should be correctly transformed
  
  ## Environment & setup
  
  <!-- In which environment does the problem occur -->
  
  - OS: <!--[e.g. Mac OS, Windows, Debian, CentOS, ...]--> Mac OS
  - Database: <!--[PostgreSQL, MySQL, MariaDB or SQLite]--> SQLite
  - Python version: <!--[Run `python -V` to see your Python version]--> 3.9.9
  - Prisma version: 3.8.1
  
  ## Additional context
  
  This is not currently solvable by us as Prisma does not give us the field name at the database level. If they did we could simply create an alias when defining the `BaseModel`:
  
  ```py
  class User(BaseModel):
      ...
      name: str = Field(alias='username')
      ...
  ```