feat(devkit): add aggregateLog util for executor to plugin migration

[Coly010]

Current Behavior

There is no way to aggregate logs and output at the end of execution for the executor to plugin migrations

Expected Behavior

There should be a way to aggregate logs and output them at the end of execution

Usage:

// Call with the executorName that is being migrated
// Make sure the log itself does not contain dynamic values
// Add the project root that is being migrated

aggregateLog({executorName: '@nx/vite:build', project: projectRoot, log: 'Encountered X in project.json. Do Y to handle this manually.'})

// Then in GeneratorCallback run a task
return () => { flushLogs() };

Example Output

Related Issue(s)

Fixes #

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Jun 13, 2024 4:49pm

[nx-cloud]

☁️ Nx Cloud Report

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

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --targets=e2e,e2e-ci --base=4a5eb23302cc68ecedf2f4733f1e9aacfb14584e --head=c332cb58be3d67dd2c2e364f6fc0cb5eca047bb7 --parallel=1
• nx affected --targets=lint,test,build --base=4a5eb23302cc68ecedf2f4733f1e9aacfb14584e --head=c332cb58be3d67dd2c2e364f6fc0cb5eca047bb7 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=4a5eb23302cc68ecedf2f4733f1e9aacfb14584e --head=c332cb58be3d67dd2c2e364f6fc0cb5eca047bb7
• nx documentation --no-dte
• nx affected -t e2e-macos-ci --parallel=1 --base=4a5eb23302cc68ecedf2f4733f1e9aacfb14584e --head=c332cb58be3d67dd2c2e364f6fc0cb5eca047bb7

---

Sent with 💌 from NxCloud.

[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.