clarify bbox parameter requirement for cube/items queries

[tomkralidis]

The bbox query is required for the following query types:

• cube
• items

However, the bbox parameter definition shows required: false.

1. cube query: https://github.com/opengeospatial/ogcapi-environmental-data-retrieval/blob/master/core/standard/openapi/paths/queries/cube.yaml
2. items query: https://github.com/opengeospatial/ogcapi-environmental-data-retrieval/blob/master/core/standard/openapi/paths/queries/items.yaml
3. bbox parameter (referenced by 1 and 2): https://github.com/opengeospatial/ogcapi-environmental-data-retrieval/blob/master/core/standard/openapi/parameters/core/bbox.yaml

This yielded errors on EDR CITE against my pygeoapi instance (CITE is testing that the OpenAPI .../cube endpoint has a required bbox parameter).

If the bbox parameter is required for all of the queries it applies to, then the bbox parameter definition needs to be updated (required: true).

Happy to PR if this is the intended behaviour.

[chris-little]

@tomkralidis As the cube query was updated from the original WKT polygon syntax to a bbox syntax, for users' convenience (and probably implementers' convenience too), I think the PR has the correct behaviour.
But, does the WKT polygon syntax need to be supported for backward compatibility? So maybe the current behaviour is correct, but we need some documentation to say both query syntaxes supported? @m-burgoyne Thoughts?

[m-burgoyne]

@tomkralidis @chris-little I there will need to be two different bbox definitions, the items query can still use the current bbox parameter definition, but there needs to be a new definition for the cube query which has a required attribute of true

[tomkralidis]

@m-burgoyne looks like the items query has bbox as required as well?

https://github.com/opengeospatial/ogcapi-environmental-data-retrieval/blob/master/core/standard/requirements/edr/query_type/item.adoc

[m-burgoyne]

@tomkralidis That is an error in the document, the Items query bbox should be optional, so that document will need to be updated

[chris-little]

@tomkralidis @m-burgoyne Is this an error only in V1.1, to be addressed in V1.2, or do we need a V1.0.2 and/or a V1.1.1?

[m-burgoyne]

@chris-little V1.0.2, V1.1.1 and v1.2