Corridor requests in EDR

[awarde96]

Is your feature request related to a problem? Please describe.
While corridor and trajectory are listed as queries in the base_edr.py file they do not seem to be supported in the environmental_data_retrieval.py file and I am unable to pass in corridor-height and corridor-width when using the corridor feature.

I am creating a plugin to retireve the data and using the base pygeoapi server, should I be overwriting the environmental_data_retrieval.py file as well as the BaseEDRProvider?

Describe the solution you'd like
I would be happy to create a branch or fork with a solution to add corridor processing to environmental_data_retrieval.py similar to how cube is processed.

I could also add support for the other features not supported as shown in the table here https://docs.pygeoapi.io/en/latest/data-publishing/ogcapi-edr.html

Describe alternatives you've considered
Forking pygeoapi to add these features myself but I would like to run the base pygeoapi server and only maintain the plugin code.

In the plugin code overwrite the environmental_data_retrieval.py file.

Additional context

[github-actions]

This Issue has been inactive for 90 days. As per RFC4, in order to manage maintenance burden, it will be automatically closed in 7 days.