Integrate Keycloak package with BigBang

Big Bang:

• Have you added a namespace.yaml in chart/templates that sets up the package's namespace
• Have you added pull secret creation to a resource? This may be in the namespace.yaml file.
• Have you added a gitrepository.yaml in chart/templates that sets up a flux GitRepository resource pointing to the package's git repository?
• Have you added a helmrelease.yaml in chart/templates that sets up a flux HelmRelease resource pointing to the package's helm chart?
• Have you added default values to the HelmRelease that need to be passed downstream to the package? For example: hostname, istio.enabled, monitoring.enabled.
• Have you added image pull secret references to the HelmRelease to be passed downstream to the package?
• Have you added other package dependencies to the HelmRelease to insure deployment order?
• Have you added a key for .yaml into chart/templates/values.yaml so override values can be passed downstream to the package?
• Have you added a valuesFrom configuration in the HelmRelease pointing to the values secret with a valuesKey equal to .yaml?
• Have you added the package into chart/values.yaml under addons? Exception: core apps do not go under addons.
• Have you added enabled: false to your chart/values.yaml and conditional statements on enabled: true for your namespace, pull secret, git repository, and helm release?
• Have you added git repo configuration to chart/values.yaml pointing to the packages git repo, helm chart path, and tag.
• Have you added a values: {} placeholder for you package in chart/values.yaml?
• Have you added any applicable default values from Fences and Party Bus to the package? Exception: Infrastructure specific implementations (e.g. AWS)
• template hostnames in ingressgateway
• integrate BigBang code with custom plugin code for v13.x to keep commit history and force push to "main" branch
• add helm test code to keycloak package
• upgrade helm chart code to latest version. currently v11
• Create new custom release image from IB image 13.x. Push it to registry.dso.mil. And update Keycloak Package code with the new image.

Additional details on definition of done need to be added for:

• Database integration <--- done
• Storage (minio) ingegration <---- not applicable
• Certificates? <---- taken care of through istio gateway integration
• SSO integration <--- not applicable