Unknown format "int32" ignored in schema at path "#/properties/status"

[savage-alex]

Describe the bug

When prism finds an integer property with format int32 it reports an error. NOTE It doesn't appear to effect the use of the tool

Checking the openAPI standard a property of type integer and format int32 should be acceptable

To Reproduce

Create a response that returns this schema schemas: ProblemDetailsModel: description: 'Implementation of [RFC7807](https://tools.ietf.org/html/rfc7807) Problem Details object. Content type should always be ```application/problem+json```. Problem type definitions MAY extend the problem details object with additional members' type: object required: - type - title - status additionalProperties: false properties: type: type: string format: uri description: 'A type URI' example: 'https://oneadvanced.com/problem/400' title: type: string description: 'A short, human-readable summary of the problem type' example: 'Bad Request' status: type: integer format: int32 description: 'The HTTP status code for this occurrence of the problem' example: 400 detail: type: string description: 'A human-readable explanation specific to this occurrence of the problem' example: 'The request is invalid.' issues: type: array description: 'A list of issues that exist with the request. Note this is an extension that is supported by the RFC but specific to Advanced.' items: type: object properties: fieldName: type: string error: type: string example: - fieldName: 'fieldName' error: 'This is the problem with the field' - fieldName: 'fieldOther' error: 'This is the problem with the field' instance: type: string description: 'A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced' example: 'https://oneadvanced.com/support/problem/74837463'

Prism will report an error (but still return the response!)

Expected behavior

No errors in the prism log