Draft: Add reassurance to the trial flow – Design 1

To-dos:

• Talk to @kcomoli, @nicolasdular, & @a_akgun to see if they know of any similar pages/layouts which already exist in the product.
• Double-check to see if @alexbuijs or @rhardarson worked on the in-app purchase flow and whether or not they think its layout could possibly be repurposed for this experiment
• Update the issue’s description section about tracking to explicitly state that we’ll be tracking using fully anonymous front-end Snowplow events
• Ping a technical writer when this MR gets closer to being ready to review some of the copy
• Export the SVGs from the Figma design spec file
  • Note: this includes the company logos
• Only show the new design for screen widths of 1150px (desktop) and above
• Experimental layout should play well with any other experiments running in the same area

What does this MR do?

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #281027 (closed)