* conditional use of --db-repository option with Bash variable expansion
* rephrase DOCKER_TRIVY_DB_REPOSITORY doc to match Trivy help

Resolve "Add java database args for trivy for using custom JAVA DB URL"

Closes #74

See merge request !108

# [5.10.0](5.9.1...5.10.0) (2024-04-02)

### Features

* **trivy:** enable custom Trivy Java DB repository ([059fda87](059fda87))

## [5.10.1](5.10.0...5.10.1) (2024-04-03)

### Bug Fixes

* **variants:** use service containers "latest" image tag (vault, GCP & AWS) ([0f57cdd7](0f57cdd7))

Today creating a backmerge MR from prod or integ branch to any other branch triggers a pipeline
even though no change has been pushed.
Ultimately those pipelines might (re)trigger integration or production environment deployment and/or packages publication.
That might have unexpected consequences.
This change simply disables MR pipeline from prod & integ branches, enforcing branch pipelines only (i.e. when a true commit is pushed).

## [5.10.2](5.10.1...5.10.2) (2024-05-05)

### Bug Fixes

* **workflow:** disable MR pipeline from prod & integ branches ([6460d7bb](6460d7bb))

Without this information, it is easy to imagine the TRACE variable was not correctly set.

chore(deps): update dependency to-be-continuous/semantic-release to v3.10

See merge request !109

ci(security): add Gitleaks scan

See merge request !110

chore(deps): update dependency to-be-continuous/semantic-release to v3.11

See merge request !111

## [5.10.3](5.10.2...5.10.3) (2024-07-01)

### Bug Fixes

* **Trivy:** Trivy 0.53.0 added the clean subcommand for semantic cache management ([e3a95408](e3a95408))