A user can be presented with the about your company page in the trial registration flow

What does this MR do and why?

It enables passing trial param passing through the registration flow. This is part of #355786 (closed)

This flow forces the user to go through a new company page - same as standard trial registration flow. The user starts at http://gdk.test:3000/-/trial_registrations/new and continues the same path as the video shown in this MR, except the trial boolean is on throughout the process since they will have gone through the trial_resgitration flow initially.

How to set up and validate locally

1. Setup prerequisites:
   1. Ensure GITLAB_SIMULATE_SAAS=true is in your environment and that you've restarted your services after setting it.
   2. Ensure that your license is up to date so that new users can be registered successfully (do we need steps documented for this?)
   3. Ensure the customers application is setup and working.
   4. Ensure admin approval for user registration is not required: (via the rails console)

      ApplicationSetting.first.update(require_admin_approval_after_user_signup: false)

   5. Ensure that email confirmations are not required: (via the rails console)

      ApplicationSetting.first.update(send_user_confirmation_email: false)

   6. Enable the following feature flags: (via the rails console)

      Feature.enable(:user_other_role_details)
      Feature.enable(:combined_registration)
      Feature.enable(:about_your_company_registration_flow)

   7. Ensure that any other feature flags that might impact the registration flows are disabled. (via the rails console)
2. Replication steps:
   1. Register a new user by visiting: http://gdk.test:3000/-/trial_registrations/new
   2. You must answer the following questions in this way to see the whole registration flow:
      1. Welcome page:
         1. Who will be using GitLab? My company or team
         2. What would you like to do? Create a new project
      2. About your company page:
         1. GitLab Ultimate trial (optional) Toggled ON
   3. Upon completion of the registration steps, verify that the expected request(s) have gone to the customers application and that they contain the expected new params.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.