make support for features/records extra query parameters configurable

[tomkralidis]

Overview

This PR enables pygeoapi, by default, to ignore extra query parameters for features/records queries.

An added provider level include_extra_query_parameters directive (true|false, default false) can control whether to enable provider support.

The update in #1673 results in all query parameters being passed and evaluated. pygeoapi's OpenAPI definition declares additionalProperties: true for all .../items endpoints by default, which allows us to evaluate extra query parameters as desired.

As a result, extra query parameters are always ignored unless set in provider config.

Related Issue / discussion

#1673

Additional information

Some CITE config fixes and removal of leftover print statements are also included in this PR.

Dependency policy (RFC2)

• I have ensured that this PR meets RFC2 requirements

Updates to public demo

• I have ensured that breaking changes to the pygeoapi master demo server have been addressed
  • https://github.com/geopython/demo.pygeoapi.io/blob/master/services/pygeoapi_master/local.config.yml

Contributions and licensing

(as per https://github.com/geopython/pygeoapi/blob/master/CONTRIBUTING.md#contributions-and-licensing)

• I'd like to contribute [feature X|bugfix Y|docs|something else] to pygeoapi. I confirm that my contributions to pygeoapi will be compatible with the pygeoapi license guidelines at the time of contribution
• I have already previously agreed to the pygeoapi Contributions and Licensing Guidelines

[doublebyte1]

+1 for making the extra parameters functionality more tightly integrated in the code. If there are any providers where enabling this is particularly important for supporting a particular behaviour, I think that should be mentioned in the documentation.

[doublebyte1]

In the case of add_param=True because of p.include_extra_query_parameters is not really a property filter, is it? I find this comment to be a bit misleading