Fix circular imports.

[wjhsf]

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)

[bfeister]

Can we get a description of what this is doing? Specifically, did this manifest as an error? If yes, how and where?

[wjhsf]

This is just moving function definitions to avoid circular imports. It's just to make the imports cleaner, there aren't currently any errors.

The base branch was changed.

[alexvuong]

a bit of context: reason we put this func and resolvePathFromUrl is to have all the multi-site util in one single file

[alexvuong]

The functions in this file is to process the given url and return a new one while resolveSiteFromUrl and resolveLocaleFromUrl is the other way around which it looks into the given url, extract and return data. I don't think they belong here 🤔

[wjhsf]

Replaced by #1133.