Pin Trivy to safe version

[jwallace94]

Overview

In the wake of the recent trivy vulnerability, this change reflects the actions taken by the PygeoAPI developers. This change is in line with ensuring there is minimal code drift as this will match the code change found in the PygeoAPI repo when we upgrade in the future.

See the following link for the change made on the PygeoAPI repo: https://github.com/geopython/pygeoapi/pull/2293/changes

Related Issue / discussion

https://gajira.atlassian.net/browse/DAT-1327

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