Bugfix: Jest test failures not surfaced in pipeline

[jongpie]

• Switched back to using sfdx-lwc-jest for running jest tests - using sf force lightning lwc test run returns 0 exit code for failures, so failures weren't being surfaced
  • @jamessimone has opened issue #2991 in the CLI's repo for this issue
  • Also upgraded several dependencies in package.json
• Fixed some failing Jest tests for logger LWC - these were previously failing due to some asserts being out of date due to the changes made in release v4.13.17, but weren't being reported by the pipeline

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.18%. Comparing base (6664ed1) to head (67b839c).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #739      +/-   ##
==========================================
- Coverage   95.44%   93.18%   -2.27%     
==========================================
  Files          51       67      +16     
  Lines        5620     6939    +1319     
  Branches        0      197     +197     
==========================================
+ Hits         5364     6466    +1102     
- Misses        256      445     +189     
- Partials        0       28      +28     

Flag	Coverage Δ
Apex	95.44% <ø> (ø)
LWC	83.54% <100.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.