@W-16909794 - Add passwordless/social login UI buttons to Checkout page

[yunakim714]

Description

To enable social and passwordless login in the PWA Kit, we need to ensure that these login methods are also available in the Checkout flow. Today, users can either check out as a GUEST or log in with an email and password.

If a customer has enabled social and/or passwordless login, we want to add these as login options.

Types of Changes

• [ ] Bug fix (non-breaking change that fixes an issue)
• [x] 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

• Modify the <ContactInfo> component that is rendered in the Checkout page
• If Social and Passwordless Login are enabled, render these login buttons
• If they are NOT enabled, maintain the original log in flow (guest or credentials)

How to Test-Drive This PR

• Enable both social and passwordless login in the config

• Verify that the ContactInfo card looks as follows:

  

• When user logs in with password, the other buttons should disappear: https://github.com/user-attachments/assets/ad917723-82df-4ebe-b6a8-253ca6c98a65

• Disable both social and passwordless login in the config

• Verify that the ContactInfo card looks as follows:

  

Checklists

General

• [x] 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

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