BO - Deep linking support for products (CPF)

[NamFra]

Feature Request

Is your feature request related to a problem or unsupported use case? Please describe.
Currently, in the B2C sales tunnel, only credit card registration is possible. This limitation prevents offering CPF (via MonCompteFormation) as an alternative for credentials eligible for this funding.

Describe the solution you'd like
We want to integrate the following in Joanie (admin and BO):

1. A deep linking activation option at the product level (in the "Syllabus" tab, which shows the product-course relationship and offerings)
2. Once activated, the possibility to associate a deep MonCompteFormation (MCF) link for each selling organization linked to the product
3. Random redirection among these links, triggered when the user clicks "Mobiliser mon CPF" in the Richie sales tunnel

• Since the CPF link is permanent and independant of sessions, it must necessarily be attached at the product level
• The input field could be integrated into the course_product_relation interface, either alongside the Offerings or when adding participating organizations

• A "Deep linking" toggle/button could be added to reveal the list of organizations (from course_product_relation_organizations) and a (facultative) deep link input per organization

Expected user path:

• Admin (Joanie BO):

1. Accesses product editing
2. Enables deep linking (for CPF eligibility)
3. Fills in one deep MCF link per participating organization
4. Can later edit these links (ideally)

• Learner (Richie) (cf. Display CPF button in sales tunnel richie#2676):

1. Accesses a course syllabus
2. Clicks on “Enroll”
3. Chooses between “Subscribe by credit card” and “Mobilise my CPF”
4. Clicks CPF
5. Gets randomly redirected to one of the MCF links entered in Joanie
   • Persisting the proposed URL during a single navigation session would be a plus, but not required

Describe alternatives you've considered

• Handling CPF link integraton in Richie (by the organizations): ruled out for V1 (lack of visibility + adds frontend complexity)
• Recording CPF orders in Joanie: not needed for V1, as learners can register directly via MCF without accessing our plateform

Discovery, Documentation, Adoption, Migration Strategy

• In V1:
  • Simple redirection, no MCF API calls
  • No link deactivation or date management
  • Manual registration validation in admin (via promo codes or other mechanisms to be implemented in Joanie)
• Later: the ability to track clicks on the CPF button, create draft orders, and follow traffic (not a V1 priority)