Fully rollout (remove) feature flag for cloudflare for Duo Workflow

Dylan Griffith (ex GitLab)requested to merge
509586-fully-rollout-cloudflare-proxy-for-duo-workflow-service into master

What does this MR do and why?

Fully rollout (remove) feature flag for cloudflare for Duo Workflow

In In #509586 (closed) we introduced a feature flag for determining whether or not to send Duo Workflow requests via Cloudflare. This was enabled per #509586 (comment 2714079014) and it seems we do not have any new networking issues.

Now we want to fully roll this out and remove the feature flag so that self-managed customers start using cloudflare.

The only change in this MR is in the default_service_url method. All it does is return the cloudflare URL now instead of the direct URL for the service. Cloudflare then proxies to this same underlying service URL.

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.

Related to #509586 (closed) Related to #559199 (closed)

Merge request reports