Add feature flag and routing for new hand raise leads endpoint

Summary

Add feature flag and routing logic on GitLab.com to support the new leads/gitlab_com/hand_raises endpoint on CustomersDot.

Problem

GitLab.com currently routes hand raise lead creation to the legacy trials_controller.rb endpoint on CustomersDot. We need to add a feature flag to gradually migrate to the new dedicated endpoint.

Implementation Details

Feature Flag

Name: new_hand_raise_lead_endpoint

Type: gitlab_com_derisk (percentage-based rollout)

• Create a feature flag rollout issue following https://docs.gitlab.com/development/feature_flags/#create-a-new-feature-flag.
• Add the issue to the current epic.

Code Changes

Locate hand raise lead creation code:

• Find where GitLab.com calls CustomersDot for hand raise leads
• Likely in a service, helper, or controller

Add conditional routing:

def hand_raise_lead_url
  if Feature.enabled?(:new_hand_raise_lead_endpoint)
    "#{customer_portal_url}/leads/gitlab_com/hand_raises"
  else
    "#{customer_portal_url}/trials/hand_raise_lead" # Legacy endpoint
  end
end

Rollout Plan

This issue creates the feature flag infrastructure. Actual rollout will be handled in a separate rollout issue following GitLab's feature flag rollout process.