W-21432256: Salesforce Payments on PWA Feature

[amittapalli]

This PR spans 3 packages with ~15,165 lines added across 120 files (including tests and translations). The changes enable Stripe, Adyen, and PayPal payment processing via the SF Payments SDK, with both standard checkout and express payment flows (Apple Pay, Google Pay, PayPal, Venmo).

Gus item: https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE00002VgsrOYAR/view

Description

This document summarizes the Salesforce Payments on PWA Feature:
https://salesforce.quip.com/UErWA4QiaiES

Areas that are common and can be reviewed further include

• changes to package,json
• changes to default.js files (template and handle-bars)
• changes to ssr.js
• commerce sdk react
• Any v1-V2 changes that might be applicable outside of Payments
• Shared Components/files:
  • ProductView
  • Routes.jsx
  • Constants.js
  • Cartmodal
  • Addressfield
  • Usecurrentbasket hook
  • Usecurrentcustomer hook
  • Checkout index
  • CheckoutContext

Areas that are Domain/Payments specific

• There are many components,hooks,changes to pages done as part of Salesforce Payments. Hopefully the attached doc will help but its pretty involved to understand the business logic

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.

[vcua-mobify]

I approved #3722 so I'll approve this since this is just squashing the commits in order to address unsigned commits.

[patricksullivansf]

Approving based on #3722