Explicit schema type specified on `@Parameter` annotation is always ignored

I am accepting a query parameter within an object in an opaque form so that I can apply Jakarta validation constraints to it, rather than failing to create the object at all and generating a useless message about dependency injection not being able to build the object.

I'm declaring a query parameter as a String and then parsing it later, as follows:

    @PositiveOrZero
    @Parameter(description = "The offset at which to list items", schema = @Schema(type = "integer", format = "int32"))
    @QueryParam(OFFSET)
    public String offset;

Despite this, the schema for the query parameter continues to have string as its type:

      parameters:
      - name: offset
        in: query
        description: The offset at which to list items
        schema:
          type: string  # should be type: integer
          format: int32

Using schema = @Schema(implementation = Integer.class) also fails to attach the correct type to the query parameter.

Start by tracing how the @Parameter and nested @Schema annotations are processed for query parameters. Reproduce the example and verify that an explicit schema type or implementation is preserved instead of being replaced by the Java field type; done means the generated OpenAPI schema reports offset as an integer with format int32.