more further pydantic/serialization options

Is your feature request related to a problem? Please describe.
The current pydantic integration is great but only one way, it's only useful for serializing and sending out data

Describe the solution you'd like
integration for deserializing models as well, this would make integrating with web frameworks that already leverage pydantic (like fastapi) much much easier

more specifically:

• a way to to make objects linked to the database based on a dict or even directly so classes can be used directly as type hints and fastapi/pydantic figure out the validation and returning of 422 (unprocessable entity) errors so we don't have to do this

• a way to then save this object to the database (saving the altered fields, primary key or unique key would ofc have to be present and valid for this to work)

Describe alternatives you've considered
doing it manually, it works but isn't great

Additional context
building an api using fastapi for handling the web requests and tortoise is my orm of choice to communicate with the database

No file or test is named. Start by locating the existing Pydantic serialization integration and reviewing how Tortoise models are used with FastAPI; define the scope for deserializing dicts or models and saving altered fields when a valid primary or unique key is present.