EDA Server API Health Checks Fail in IPv6 only

When using IPv6 as the main ip in pods (as noted by status.podIP) the healthchecks fail for eda-storage-api.

I believe this is related to [gunicorn only binding to v4](https://github.com/ansible/eda-server-operator/blob/b04762bca58750aa62c15aecda3725e2535c52d0/roles/eda/templates/eda-api.deployment.yaml.j2#L203). In our cluster I have worked around this by disabling the operator and changing the deployment to `gunicorn --bind '[::]:8000' --workers 2 aap_eda.wsgi:application`.

I'm not sure if changing that globally is the best answer so I am submitting this issue.

We are running operator 1.0.2.

Start at roles/eda/templates/eda-api.deployment.yaml.j2 around line 203 and compare the current gunicorn binding with the IPv6 workaround in the issue. Verify the resulting deployment allows eda-storage-api health checks to pass when pods use IPv6 addresses, while preserving the existing behavior where appropriate.

Written by the indexing model from the issue text.