Following on bug 1842913, when the optedIn pref is available, and following bug 1844097, when the shopping page has been updated to get its initial data from the child actor, we will want to update the shopping container code to handle the optedIn pref as part of that bundle:

If the optedIn pref value is 0, the user has not gone through onboarding yet, so we will want to only render the header component and nothing else. The OMC code will then render a card in the remaining space in the page.

The OMC code will separately check the pref and render itself inside the <div id="multi-stage-message-root"> being added in bug 1839764, so I don't think we will need to coordinate component rendering within the page--but if things get weird between our web component code and the react code, this could be the reason.

If the optedIn pref value is 1, the user has opted in to the shopping experience, and we'll want to render the page as usual.

If the optedIn pref value is 2, the sidebar will not open at all, so I don't think the shopping page code needs to handle this value.