Read data about selected integration connectors

[jst-cyr]

This change will read the data from the user and parse it into objects so that can be used in Outcomes later to make decisions on which tiles to show or which content recommendations to make.

Additionally, this fixes the Cypress tests so that they can incorporate the new question into the flow.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
sitecore-migration-game	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 12, 2024 4:47pm

[thomas-desmond]

Approved.

This does bring to light how limiting our current multi-select implementation is. It would be nice to have the none logic built into the multi-select rather than handled in the GameContextParser but that's a larger refactor that should not be in this PR.

[jst-cyr]

This does bring to light how limiting our current multi-select implementation is. It would be nice to have the none logic built into the multi-select rather than handled in the GameContextParser but that's a larger refactor that should not be in this PR.

Yes, we likely need a new type of control (we only have two right now). Something that is a "none-able" multi-select which renders a special none button but mostly behaves like multi-select. Then we can handle it on the Prompt to specify to use that control type instead of multiselect.