Reject boolean values for the limit parameter

[Shubham-Padkonde]

get_typed_value turns limit=true into the boolean True, which passed the isinstance(..., int) check because bool is a subclass of int, so evaluate_limit returned True as the limit (and limit=false failed with "should be strictly positive"). Booleans are now rejected with the same "should be an integer" error as other non-integer values.

Overview

Related Issue / discussion

Additional information

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

[Shubham-Padkonde]

The current Build failure is in PostgreSQL provider setup: all 42 failed cases in #2419 and #2420 raise ModuleNotFoundError: No module named 'psycopg'; 382 tests pass in each run. The failing cases use the shared connection_string fixture with postgresql://..., while the current provider requirements install psycopg2 only. Neither PR changes these provider requirements or fixtures.

Logs: https://github.com/geopython/pygeoapi/actions/runs/36156172783 and https://github.com/geopython/pygeoapi/actions/runs/36156196416.

Would you prefer the shared fixture to specify postgresql+psycopg2://, or to add psycopg 3 support to the provider test environment? I have left that broader driver choice outside these two fixes. Diagnosis prepared with Codex assistance.