feat(repo): add new flag for verbose e2e logging

[meeroslav]

Existing NX_VERBOSE_LOGGING is too broad for E2E tests and creates a lot of noise in the output.
The new NX_E2E_VERBOSE_LOGGING reports just relevant logs.

Current Behavior

Expected Behavior

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated
nx-dev	⬜️ Ignored (Inspect)	Visit Preview		Mar 13, 2023 at 5:10PM (UTC)

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 3339c5a. 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 8 targets

• nx run-many -t e2e-macos --parallel=1 --exclude=e2e-detox
• nx affected --target=e2e --base=467be2011d36f65d63820094264db21944bf1e43 --head=3339c5a08ecea205c973fda2bbfe6bd93aa49eb2 --exclude=e2e-storybook,e2e-storybook-angular --parallel=1
• nx run-many -t root-lint check-imports check-commit check-lock-files depcheck --parallel=1 --no-dte
• nx affected --target=test --base=467be2011d36f65d63820094264db21944bf1e43 --head=3339c5a08ecea205c973fda2bbfe6bd93aa49eb2 --parallel=1
• nx affected --target=build --base=467be2011d36f65d63820094264db21944bf1e43 --head=3339c5a08ecea205c973fda2bbfe6bd93aa49eb2 --parallel=3
• nx affected --target=lint --base=467be2011d36f65d63820094264db21944bf1e43 --head=3339c5a08ecea205c973fda2bbfe6bd93aa49eb2 --parallel=3
• nx-cloud record -- nx format:check --base=467be2011d36f65d63820094264db21944bf1e43 --head=3339c5a08ecea205c973fda2bbfe6bd93aa49eb2
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[barbados-clemens]

@mandarini is also refactoring the e2e utils to add the isVerbose() check in places to probably a merge conflict coming for one of y'all.

[meeroslav]

@mandarini is also refactoring the e2e utils to add the isVerbose() check in places to probably a merge conflict coming for one of y'all.

Yes, the two of us are in sync.

[mandarini]

My PR caused these merge conflicts, I can fix them tomorrow to keep the logic I intended. If @vsavkin @FrozenPandaz can take a look in the meantime and see if this can be approved, so we can merge tomorrow morning our time, after conflicts are fixed?

[meeroslav]

I have rebased it @mandarini. We do need the review though.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.