Description

Disable REST EDS server by default, which is no longer necessary now that upstream envoy has fixed envoyproxy/envoy#13070

Context

REST EDS was a workaround to avoid the bug in envoy, but we now depend on envoy-gloo 1.17.0-rc3 which itself depends on envoy https://github.com/solo-io/envoy-gloo/blob/master/bazel/repository_locations.bzl#L4 from commit 6be36debaf627925ebf5e22e84e7e066191b14d5

Checklist:

• I included a concise, user-facing changelog (for details, see https://github.com/solo-io/go-utils/tree/master/changelogutils) which references the issue that is resolved.
• If I updated APIs (our protos) or helm values, I ran make install-go-tools generated-code to ensure there will be no code diff
• I followed guidelines laid out in the Gloo Edge contribution guide
• I opened a draft PR or added the work in progress label if my PR is not ready for review
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
  BOT NOTES:
  resolves [Migrated] Enable rest XDS for endpoints to fix race condition in envoy solo-io/gloo#3805