test(atomic): start tests on atomic-commerce-facets

[olamothe]

Mostly: Add new base-page-object to inherit from for each tests, which should simplify/streamline the "load this story for this component with these arguments in the URL" repetitive pattern.

https://coveord.atlassian.net/browse/KIT-3256

[developer-experience-bot]

Pull Request Report

PR Title

❌ Title should follow the conventional commit spec:
<type>(optional scope): <description>

Example: feat(headless): add result-list controller

Live demo links

• Storybook

• Playwright report

Bundle Size

File	Old (kb)	New (kb)	Change (%)
case-assist	204.8	204.8	0
commerce	292.6	292.6	0
search	372.3	372.3	0
insight	352.3	352.3	0
product-listing	266.9	266.9	0
product-recommendation	170.8	170.8	0
recommendation	217.8	217.8	0
ssr	365.1	365.1	0

SSR Progress

Use case	SSR (#)	CSR (#)	Progress (%)
search	39	44	89
recommendation	0	4	0
product-recommendation	0	10	0
product-listing	0	13	0
case-assist	0	6	0
insight	0	27	0
commerce	0	15	0

Detailed logs

search : buildInteractiveResult
search : buildInteractiveInstantResult
search : buildInteractiveRecentResult
search : buildInteractiveCitation
search : buildGeneratedAnswer
recommendation : missing SSR support
product-recommendation : missing SSR support
product-listing : missing SSR support
case-assist : missing SSR support
insight : missing SSR support
commerce : missing SSR support

[louis-bompart]

I'm not fond of those tests/utils if I'm perfectly honest.
I think we should try to adhere more closely to the modern test philosophy shared across all modern test frameworks, which entails testing user-visible behaviour.
https://playwright.dev/docs/best-practices#test-user-visible-behavior
https://testing-library.com/docs/guiding-principles

What does that mean for this PR?

1. packages/atomic/src/components/commerce/facets/atomic-commerce-facets/e2e/page-object.ts should have locators built around the facet labels
2. The utils should make lighter uses of the hydrated selector.