fix(envoy): add readiness probe to Envoy

[SDJustus]

What this PR does / why we need it:
this PR adds a readiness prove to envoy to prevent it from getting traffic while not being able to handle the requests. Primarily this is needed, if the pod starts/restarts.
Which issue(s) this PR fixes:

Fixes #5157

Special notes for your reviewer:
I was first thinking about adding a startup probe for this, but the kubernetes docs state, that this is mostly done for slow starting services and I don't think the envoy is one. On my cluster, the envoy restart/start takes between 10 and 15 seconds so the initial delay of 10 seconds and 3 retries every 5 seconds should be sufficient.
I couldn't see any problems with controller after the health check was added.

[seldondev]

Hi @SDJustus. Thanks for your PR.

I'm waiting for a SeldonIO or todo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

[agrski]

I've done two things to test this, having checked out the PR:

• I've tried running make -C operator create and confirmed there are no changes.
• I've tried installing the updated chart into an existing kind cluster, confirmed the probe is now set, and confirmed that k8s doesn't mark the pod as ready instantly. In fact, when port-forwarding the admin port I was able to hit the /ready endpoint before it was ready and confirmed the statuses being sent then and after readiness (503 and 200 respectively).