Minor schema validation error: doesn't complain about invalid default for null and file types

Describe the bug
NoneProperty.build and FileProperty.build do have logic to detect if a default other than None was provided for a null property, or if any default was provided for a binary string—and we do have unit tests for those. However, in reality NoneProperty.build and FileProperty.build do not actually get called, because property_from_data just calls the initializers directly instead. Therefore if you do something like this, the default is simply ignored.

OpenAPI Spec File

components:
  schemas:
    MyModel:
      properties:
        myNullProperty:
          type: "null"
          default: "definitely not null"
        myBinaryString:
          type: string
          format: binary
          default: "???"

Desktop (please complete the following information):

• OS: any
• Python Version: any
• openapi-python-client version: 0.21.6

Start by tracing property_from_data and compare its direct initializer calls with NoneProperty.build and FileProperty.build, which already contain validation logic. Run the existing unit tests for those builders, then add coverage showing that invalid defaults in the provided OpenAPI schemas are rejected rather than ignored.