Supporting of one separate 'required' option for query parameters

[Morgunov-Vitaly]

Hi!
For example, there are several paths that include similar parameters, but with different required options: in some paths parameters are required, in others they are optional.

If we can specify the required option separately, we can reuse parameter descriptions. Like this:

/api/v1/rootname:
 get:
 summary: 'Path example'
 parameters:
 - $ref: '#/components/parameters/queryFiltersDateFrom'
 - $ref: '#/components/parameters/queryFiltersDateTo'
 - $ref: '#/components/parameters/queryGroups'
 - $ref: '#/components/parameters/queryOrderByColumn'
 - $ref: '#/components/parameters/queryOrderByDirection'
 required:
 - 'filters[date_from]'
 - 'filters[date_to]'
 - 'groups'
 - 'order_by_column'
 - 'order_by_direction'

[hkosova]

Related (or duplicate): #2026

[handrews]

This is supported for query parameters in 3.2 through PR #4590 by modeling all query parameters in a single schema, which lets you use the regular required for this. We will consider further work in future releases.