feat: enable skip on information screens

[sshanzel]

Changes

• There are two things that was introduced here:
  • First is the support on Info screens to have a "Skip" button.
    • This also introduced support for custom copy for the button and its placement.
    • See it in action through the recording.
  • Second is the support for destination with next value.
    • This change will make it easier to track what was the previous intention for enabling the Skip. Whether it was just to move on to the next step, or to actually jump to another screen. This helps when product is trying to move things around.
    • Everything involved in this change was isolated in this commit. I encourage you to take a peek at this first to make it easier to identify the distinction between the changes: d3ec265

See it in action:
https://github.com/user-attachments/assets/6f8353d5-04e5-4907-a263-4cfe2a3db52b

Events

Did you introduce any new tracking events?

Experiment

Did you introduce any new experiments?

Manual Testing

Caution

Please make sure existing components are not breaking/affected by this PR

Jira ticket

MI-895

Preview domain

https://mi-895.preview.app.daily.dev

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
daily-webapp	✅ Ready (Inspect)	Visit Preview	May 16, 2025 9:38am

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
storybook	⬜️ Ignored (Inspect)		May 16, 2025 9:38am

[ilasw]

Why are we putting cta and placement in transition? 👀

imo those infos should be added in step.parameters inside a dedicated property, something like step.parameters.ctas:

Array<{ label: '', type: FunnelStepTransitionType, placement: '...' }>

or (for easier access)

step.parameters[PLACEMENT] : { label: '', type: FunnelStepTransitionType } 

Doing so we are separating the UI infos from the logic ones. Wdyt?