Geoparquet 1.1 spec compliance update

[C-Loftus]

Overview

This PR address #2252

• If a parquet file has a bbox column, it will be filtered with using the bbox instead of needing to specify multiple x / y columns
• Added support to allow for id columns that are strings other other types. Previously it just used the row index of the data as the id value no matter what. This caused issues when the id was a string.
  • I added a warning log if the id column is non-numeric. Parquet cannot calculate row statistics as easily for strings or other non-numeric types, and as such, queries are likely to be less efficient
• Cleaned up some of the internals; previously there were some dangling variables or unclear semantics on how the bbox filter works
• Cleaned up tests. There is one class for all naive parquet files (i.e. ones that don't follow the geoparquet spec and naively set a point column) and one for all geoparquet compliant files

Related Issue / discussion

Closes #2252

Additional information

• In the future it would be useful to change all code in this provider to skip the pandas serialization step. It is generally not necessary and adds extra overhead to convert to the intermediate format. However, for the sake of not making too many changes in one PR, I've left it as is.

• I have not changed any of the code for s3fs. It is possible this could be tweaked for better performance.

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

[C-Loftus]

Few comments on anything non obvious

[C-Loftus]

Raises a specific error instead of generic exception

[C-Loftus]

This variable self.bb was unused

[C-Loftus]

To my understanding pyarrow more efficiently creates the scanner when calling with the method on the object.

Feel free to let me know if you prefer removing use_threads or tweaking other kwargs here

[C-Loftus]

No need to store this as a variable since we always just return the result directly

[tomkralidis]

@C-Loftus can you address the CI errors? Thanks in advance.

[C-Loftus]

Fixed! Sorry I missed that

[C-Loftus]

Thanks for your review and feedback! I will prioritize addressing this as soon as I have some time, most likely early next week

[C-Loftus]

Thanks again for your review. I believe I should have all feedback addressed.

The one extra change I made in the latest commit is to remove some of the dangling variables from get_test_file_path and just put them directly in the fixture so its is clearer they are only used once and what fixture they correspond to.