Swagger/struct generation now uses concrete types exclusively to simplify config object setup

[Tanz0rz]

oapi-codegen is the tool used to convert an OpenAPI spec file into Golang structs. By default, it sets optional parameter types to pointers, but this leads to clunky configuration for the user. This PR updates the swagger files in-place to append oapi-codegen's custom field x-go-type-skip-optional-pointer to all parameters and schemas in the swagger spec.

If possible, this should be done in a more native way (potentially using oapi-codegen's template framework). The current approach uses jq to update the swagger spec and could lead to unexpected behavior in at least two scenarios:

1. Response objects no longer have pointers. This means lots of "zero" values will come back on these structs when parsing API responses. This will lead to clunky response objects at best and confusing responses at worst.
2. The jq command is a blanket update to the swagger files and likely does not cover all edge cases. We will need to monitor this as more services are added/updated

An issue was opened here on the oapi-codegen repo to ask the developers directly for a potential alternative to the jQuery approach.