BinarySchema V2 to V3 conversion results in StringSchema being used..

When using the V3 maven plugin, and a V2 schema with a property such as:

          secret:
            type: string
            format: binary
            minLength: 32

In https://github.com/swagger-api/swagger-parser/blob/master/modules/swagger-parser-v2-converter/src/main/java/io/swagger/v3/parser/converter/SwaggerConverter.java#L951

            result = Json.mapper().convertValue(schema, Schema.class);

schema goes in as BinarySchema (v2) and result comes out as StringSchema (v3)..

This is using swagger-parser-v2-converter 2.0.15.

Start at modules/swagger-parser-v2-converter/src/main/java/io/swagger/v3/parser/converter/SwaggerConverter.java around line 951 and reproduce the V2 YAML example through the V3 Maven plugin. Check why converting the V2 BinarySchema produces a V3 StringSchema. Done means the binary property remains represented as the appropriate binary schema after conversion, with its stated constraints preserved.