test: add e2e smoke tests for headless-ssr utils

[mrrajamanickam-coveo]

• Add e2e cypress smoke tests using the headless-ssr sample page
  • Add a corresponding new GH action to run these tests
• Modify sample page to include a timestamp
  • This is then parsed by the tests to verify the page is rendered in both SSR and CSR

Check before merging

• Cypress v12 is being used
• Next CI cache is being used Next Cache needs to be moved to root for GH cache action to work. Can revisit when next build times are significant.

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

[github-actions]

Dependency Review

The following issues were found:

• ✅ 0 vulnerable package(s)
• ✅ 0 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ⚠️ 4 package(s) with unknown licenses.

See the Details below.

License Issues

package-lock.json

Package	Version	License	Issue Type
@types/react	18.2.20	Null	Unknown License
@types/node	20.4.9	Null	Unknown License

packages/samples/headless-ssr/package.json

Package	Version	License	Issue Type
@types/react	18.2.20	Null	Unknown License
@types/node	20.4.9	Null	Unknown License

Allowed Licenses: 0BSD, Apache-2.0, Apache-2.0 AND MIT, Apache-2.0 AND BSD-3-Clause AND Python-2.0, Beerware, BlueOak-1.0.0, BSD-1-Clause, BSD-2-Clause, BSD-2-Clause-Patent, BSD-2-Clause-Views, BSD-2-Clause AND MIT, BSD-3-Clause, BSD-3-Clause-Attribution, BSD-3-Clause-Clear, BSL-1.0, CC-BY-3.0, CC-BY-4.0, CC0-1.0, CNRI-Python, curl, HPND, IBM-pibs, ImageMagick, ISC, JSON, MIT, MIT-0, MIT AND Python-2.0, MIT-advertising, mpi-permissive, NCSA, ODC-By-1.0, PDDL-1.0, Plexus, PostgreSQL, PSF-2.0, Python-2.0, Python-2.0.1, SAX-PD, Unlicense, UPL-1.0, W3C, Wsuipa, WTFPL, X11, X11-distribute-modifications-variant, Xerox, Zlib, ZPL-2.1

Scanned Manifest Files

package-lock.json

• @eslint-community/regexpp@4.5.1
• @eslint-community/regexpp@4.6.2
• @eslint/eslintrc@2.1.1
• @eslint/js@8.46.0
• @next/eslint-plugin-next@13.4.13
• @types/node@20.4.9
• @types/node@16.18.40
• @types/react@18.2.20
• commander@6.2.1
• cypress@12.17.3
• cypress-real-events@1.10.0
• cypress-web-vitals@4.0.1
• eslint@8.46.0
• eslint-config-next@13.4.13
• eslint-plugin-react@7.33.1
• eslint-scope@7.2.2
• eslint-visitor-keys@3.4.2
• minimist@1.2.8
• prettier@3.0.1
• semver@7.5.4
• @eslint-community/regexpp@4.5.1
• @eslint/eslintrc@2.1.0
• @eslint/js@8.44.0
• @next/eslint-plugin-next@13.4.12
• @types/node@20.4.5
• @types/react@18.2.17
• @typescript-eslint/parser@5.62.0
• @typescript-eslint/scope-manager@5.62.0
• @typescript-eslint/types@5.62.0
• @typescript-eslint/typescript-estree@5.62.0
• @typescript-eslint/visitor-keys@5.62.0
• eslint@8.45.0
• eslint-config-next@13.4.12
• eslint-plugin-react@7.33.0
• eslint-scope@7.2.1

packages/samples/headless-ssr/package.json

• @types/node@20.4.9
• @types/react@18.2.20
• cypress@12.17.3
• cypress-web-vitals@4.0.1
• eslint@8.46.0
• @types/node@20.4.5
• @types/react@18.2.17
• eslint@8.45.0

[github-actions]

Pull Request Report

PR Title

✅ Title follows the conventional commit spec.

Bundle Size

File	Old (kb)	New (kb)	Change (%)
case-assist	181.7	181.7	0
search	342.6	342.6	0
insight	296.6	296.6	0
product-listing	285.5	285.5	0
product-recommendation	156	156	0
recommendation	192.2	192.2	0
ssr	173.5	173.5	0

[louis-bompart]

Look nice!
Wondering how we should proceed regarding Cypress:

• use the same version as the other packages but then have another package to update when we do the update batch
• use the latest version and saves one update, but be out-of-sync with the other package, causing us to install cypress twice

[btaillon-coveo]

Wondering how we should proceed regarding Cypress:

• use the same version as the other packages but then have another package to update when we do the update batch
• use the latest version and saves one update, but be out-of-sync with the other package, causing us to install cypress twice

I personally really don't mind either way, I don't think the differences are gonna be that significant.