[Einstein analytics] Track the no-search-results scenario properly (@W-15153723@)

[vmarta]

In the case of no-search-results, it was initially sending the wrong data to Einstein. The viewSearch event should contain empty products=[] and showProducts=false.

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

1. Visit https://localhost:3000/global/en-GB/search?q=sdafdsaf
2. As expected, there is no search result for the keyword "sdafdsaf"
3. In the Network tab, inspect the viewSearch request. It should return 200 status code.

(FYI initially we saw 400 error, with the message "Must provide a products array")

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)

[vcua-mobify]

Thanks for fixing this @vmarta