fix(integ-tests): tests need to mved before they can be run

[rix0rrr]

For historical reasons of working with Jest 27 or lower, we needed to mv the integ-tests out of an install directory where they would be left by an npm install. The reason was that Jest 27 or lower would always ignore all node_modules direcotries, and so could not be configured to run tests from an install location.

Since we are on Jest 29, we can now lift this limitation with the right configuration options. We can run the tests directly from the node_modules directory and don't have to fiddle around with moving files anymore.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.15%. Comparing base (e1a9030) to head (8a04935).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #439   +/-   ##
=======================================
  Coverage   79.15%   79.15%           
=======================================
  Files          54       54           
  Lines        6889     6889           
  Branches      773      773           
=======================================
  Hits         5453     5453           
  Misses       1418     1418           
  Partials       18       18           

Flag	Coverage Δ
suite.unit	79.15% <ø> (ø)

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.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.