fix: support imports without extensions in cypress webpack build

[d-rowe]

Description

When migrating to cypress v12, we saw a small number of regressions due compilation failures in cypress. This change is to resolve this class of issue. Once resolved in this branch I'll create a PR to merge the cypress 12 upgrade in main.

Details
By default, cypress' internal webpack preprocessor doesn't allow imports without file extensions. This makes our life a bit hard since if any file in our testing dependency graph has an import without the .js extension our cypress build will fail.

This configuration relaxes this a bit by allowing imports without file extension
ex. import module from './module'

Changelog

• fix: support imports without extensions in cypress webpack build

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (cypress-unification@d7b9046). Learn more about missing BASE report.

Additional details and impacted files

@@                  Coverage Diff                   @@
##             cypress-unification    #8993   +/-   ##
======================================================
  Coverage                       ?   60.87%           
======================================================
  Files                          ?     3802           
  Lines                          ?    91070           
  Branches                       ?    14374           
======================================================
  Hits                           ?    55443           
  Misses                         ?    32086           
  Partials                       ?     3541           

Flag	Coverage Δ
Linux_1	29.02% <ø> (?)
Linux_2	56.39% <ø> (?)
Linux_3	37.89% <ø> (?)
Linux_4	29.00% <ø> (?)
Windows_1	29.03% <ø> (?)
Windows_2	56.34% <ø> (?)
Windows_3	37.90% <ø> (?)
Windows_4	29.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[d-rowe]

Related: #4813

[ananzh]

I don't think we need AGGREGATION_VIEW: false and ML_COMMONS_DASHBOARDS_ENABLED: true but I also don't think it is hurtful. But can clean up in a follow-up if we need a more cleaned up config file.