[pydantic_v2.BaseModel] Field specified as date-time is generated as AwareDatetime

[benverhees]

Is your feature request related to a problem? Please describe.
A field, specified as a date-time is generated as AwareDatetime when the output model type is pydantic_v2.BaseModel, requiring a timezone to be specified.
While I understand it is best practice to work with timezones, not all systems have a timezone stored with their date-time data.

Describe the solution you'd like
I would like it to be possible to opt out of the AwareDatetime type, and use a type that doesn't require a timezone to be specified.

Describe alternatives you've considered
I have considered monkey-patching the generated code, but that doesn't feel right, and I have looked at the possibility to set a default timezone for AwareDatetime, but that doesn't seem to exist.

[benverhees]

I just found #1735, so I understand this was driven by the openapi spec.