updated helm chart to use latest v6.0.1 version of the image (#382)

* updated helm chart to use latest v6.0.1 version of the image

* updated workflow to run against multiple k8s versions

charts/hapi-fhir-jpaserver/Chart.yaml

@@ -7,9 +7,11 @@ sources:
   - https://github.com/hapifhir/hapi-fhir-jpaserver-starter
 dependencies:
   - name: postgresql
-    version: 11.1.19
+    version: 11.6.2
     repository: https://charts.bitnami.com/bitnami
     condition: postgresql.enabled
+appVersion: v6.0.1
+version: 0.9.0
 annotations:
   artifacthub.io/license: Apache-2.0
   artifacthub.io/changes: |
@@ -17,13 +19,27 @@ annotations:
     # added, changed, deprecated, removed, fixed, and security.
     - kind: changed
       description: |
-        updated HAPI FHIR starter image to 5.7.0
+        BREAKING CHANGE: updated HAPI FHIR starter image to v6.0.1.
+        See <https://github.com/hapifhir/hapi-fhir/releases/tag/v6.0.0> for all application changes.
     - kind: changed
       description: |
-        BREAKING CHANGE: updated included PostgreSQL-subchart to v11
+        updated included PostgreSQL-subchart to v11.6.2
+    - kind: fixed
+      description: |
+        use a fixed image for the wait-for-database container (docker.io/bitnami/postgresql:14.3.0-debian-10-r20)
+        instead of relying on the PostgreSQL sub-chart values
     - kind: changed
       description: |
-        BREAKING CHANGE: removed ability to override the image flavor.
-        The one based on distroless is now the new default.
-appVersion: v5.7.0
-version: 0.8.0
+        expose actuator/metrics endpoint on a separate port (8081)
+    - kind: added
+      description: |
+        support for monitoring metrics using ServiceMonitor CRDs
+    - kind: changed
+      description: |
+        switched liveness and readiness probes to Spring Boot actuator endpoints
+    - kind: changed
+      description: |
+        BREAKING CHANGE: removed included `NetworkPolicy`, which is subject to more thorough rework
+    - kind: added
+      description: |
+        allow configuring `topologySpreadConstraints` for the deployment