@W-18034005 - [POC] Implement hybrid auth compatibility for PWA Kit v2.x

[shethj]

Description

As a hybrid auth stakeholder, I'd like to know the exact code changes required to make hybrid auth compatible with PWA Kit v2.x. Once the code changes are frozen, I can estimate the effort required for customer adoption for the same.

Outline of changes required for POC:

1. Update session sync between pwa and sfra in commerce-api

• Current logic in v2.x: pwa kit saves a copy of the refresh token in local storage. For each SCAPI request, the key and value in the localstorage is compared with that in the cookies. If either key or value doesn’t match, the accessToken is considered invalid and refresh_token flow is executed.

• Updated logic: Leverage cc-at cookie coming in from SFRA and consume directly if found in cookies on PWA Kit side.

2. Server Affinity Changes

• v2.x commerce-api updated to send dwsid header with all OCAPI/SCAPI calls for server affinity
• v2.x commerce-api updated to remove calls to OCAPI /sessions

3. Hybrid Auth Support

• Allowed cookie passthrough in commerce-api fetch calls to SLAS

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

• Updated commerce-api storage structure to manage local/cookie/memory storage
• Updated logic to sync sessions between SFRA & PWA Kit stores.
• Added sfdc_dwsid header to all OCAPI/SCAPI calls
• Allowed cookie passthrough for SLAS calls in commerce-api

How to Test-Drive This PR

• Smoke test phased launch test cases using https://dev.phased-launch-testing.com

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)

[unandyala]

LGTM