@W-21038080: Rework to use billing address phone number for guest shoppers

[dannyphan2000]

Found in BOPIS, or when we switch BOPIS -> Ship (Guest shopper). Phone number does not get persisted if we leave Checkout and come back for guest shoppers.

Result: Phone number field (in Contact Info) is not showing in Summary view. When trying to hit Edit, I do see that field populated, but when I hit continue, it's not there...

Expected: Phone number field should be visible in Contact Info summary view if filled out

Using basket.billingAddress.phone to store guest shopper’s phone number.
We use billing phone temporarily in the guest basket just to get around the issue of going back and forth from checkout to cart or elsewhere. Then update new customer profile with billing address phone. But don’t update order with billing phone because from a shopper’s perspective, they are entering their contact number and not the billing phone number.

Description

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.

[dannyphan2000]

This is a fix for redundancy (we have this method in 2 different places, one-click-payment AND index.jsx - main entry code)