Revert enabling Cloudflare for all gRPC traffic for Duo Workflow Service

What does this MR do and why?

Revert "Merge branch '509586-fully-rollout-cloudflare-proxy-for-duo-workflow-service' into 'master' "

This reverts commit 5597e267, reversing changes made to 452cb237.

See &19253 (comment 2750022218) .

We seem to have some evidence that hanging agentic chats are happening only when connections go through Cloudflare. It's not exactly clear if Cloudflare is blocking gRPC messages but the logs we have so far suggest that the receiver is not getting some gRPC messages when using Cloudflare.

For that reason we want to disable this now and confirm that the reliable bugs in that epic are resolved and then we'll need to come back and investigate what the actual reason for dropping messages is.

As described in the linked issue the use of Cloudflare is not actually useful on GitLab.com anyway. This is because the traffic is already originating from workhorse so it's an extra round trip and back into our network. It may still be useful for self-managed customers where their workhorse deployments need to connect into our network but even then they'll likely be seeing these locked agentic chats so we'll probably need to continue investigating this anyway.

References

Screenshots or screen recordings

Before	After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.