Ensure Gloo pod starts and serves EDS regardless of config errors

[lgadban]

Describe the bug
If there are user config errors that would normally prevent Gloo from starting up, we still need the control plane to be able to serve EDS updates

To Reproduce

Expected behavior
EDS updates should occur in all scenarios when the pod is running
On start up, even when config errors are present, EDS should still function

Additional context