Updated OpenAPISpecWriter & Parameter classes to allow for the optional 'format' modifier field to be included in the output schema.

[ArclightHub]

What does this change do?

Updates the output openapi.yml file to allow the optional 'format' modifier as per the swagger data-types spec:
https://swagger.io/docs/specification/data-models/data-types/

How does it work?

• Both of the Parameter classes have a new "public ?string $field = null;" property which can be optionally set to a string.
• The OpenAPISpecWriter class will include the above optional property in the 'schema' when it is set to a valid string.

[shalvah]

Sorry I didn't get to the opened issue earlier, but this doesn't sit well with me.

For one, adding a field to the Parameter DTO that is only relevant for the OpenAPIWriter does not seem right. The field is not used anywhere else in Scribe, and there isn't even a way to specify or hint its value via the default methods.

[shalvah]

On the flip side, there's probably an argument to be made for adding a custom field to the Parameter class, like we did for endpoint metadata, where Scribe can put in extra data like an inferred format, but that's a thing for another day.

I think what I'll go with for now is this:

1. I'll add a custom field to the Parameter class. You can put in whatever values you want here.
2. You can then create your own subclass of the OpenAPISpecWriter that reads the format from there, and bind to the container, and Scribe will automatically pick that instead.

[shalvah]

v3.20 will contain the new custom field. You can write/read it however you wish. https://scribe.knuckles.wtf/laravel/reference/plugin-api#__invokeextractedendpointdata-endpointdata-array-routerules-array