fix: use wdio configPath relative from workspace root to run wdio

[Roozenboom]

Current Behavior

When the e2e executor is used it runs wdio with a generated config file. This file is stored in the root of the e2e project and is referenced only by the file name. We create a child process to run wdio and configure the working directory (cwd) to the e2e project. With NPM this worked as expected, but when the project is using yarn as a package manager the working directory is not set correctly, resulting in an error Could not execute "run" due to missing configuration file

Expected Behavior

This PR changed how we configure the generated configuration in the child process command. Instead of the file name we use the file path relative to the workspace root. We also update the import path for the base configuration to always be relative to the generated config location.

Related Issue(s)

Fixes #13

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 28acfaa. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 4 targets

• nx affected --target=test --parallel=3 --ci --code-coverage
• nx affected --target=lint --parallel=3
• nx affected --target=build --parallel=3
• nx-cloud record -- npx nx format:check

---

Sent with 💌 from NxCloud.

[github-actions]

🎉 This PR is included in version 1.5.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀