feat: pd-support @W-21227485

[mjuraschik]

Description

Page Designer OOTB Support with PWA:

Brings in storefront-next-runtime package for PD design support
Aligns Page, Region and Component components with patterns for design mode
Added components needed for easier isml to react migration

• New version of ShopperExperience components in commerce-sdk-react; Old components still kept for backwards compatibility
• template-retail-react-app updated to have PD integration by default

Types of Changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

• Removing a public function or component or prop
• Adding a required argument to a function
• Changing the data type of a function parameter or return value
• Adding a new peer dependency to package.json

Changes

• (change1)

How to Test-Drive This PR

• (step1)

Checklists

General

• Changes are covered by test cases
• CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

• There are no changes to UI

or...

• Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
• Changes comply with WCAG 2.0 guidelines levels A and AA
• Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

• Changes include a UI text update in the Retail React App (which requires translation)

[cc-prodsec]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[mjuraschik]

Follow up PR from #3654 (was created from a Fork)

[mjuraschik]

Deployed here https://cc-phoenix-dreamforce-demo.sfdc-ckzqgc-ecom1.exp-delivery-soak.com/

[alexvuong]

Need PR link

[mjuraschik]

added

[alexvuong]

Have you tried testing this PR on a generated project? You may need to override the react-router package as well, the react-router required in pwa-kit template is v5, but we are asking >=7.0 in peerDependency, if the depedencies not aligned, when you first start generated project, npm i will fail unless you use npm i --legacey-run-dep which we don't want customers to do.

"peerDependencies": {
        "@react-router/fs-routes": ">=7.0.0",
        "@react-router/dev": ">=7.0.0",
        "react": ">=19.0.0",
        "react-dom": ">=19.0.0",
        "react-router": ">=7.0.0"
    },

To test generation locally,

GENERATOR_PRESET=retail-react-app-demo node packages/pwa-kit-create-app/scripts/create-mobify-app.js --outputDir ./preset-retail-react-app-demo

[mjuraschik]