feat(misc): add more logging while running migrations

[DanielRose]

Current Behavior

When running migrations, the user currently only sees any logging feedback when a migration has done any changes.

This causes the following problems:

1. Especially for large codebases and/or long-running migrations, this can result in nothing being shown for a long time. In my case, running the migrations for Nx 18 => 19 (which also upgrades Angular 17 => 18) this takes several hours, with almost no feedback on what has been done so far.
2. Before the migrations are run, they are sorted. However, the sorted list is not displayed to the user. The user may be confused as to why a migration is run "out-of-order". Also, if the migrations are aborted (either manually or due to a crash), it is difficult for the user to know which migrations have been run already, and thus could be skipped.

Expected Behavior

This adds some more logging:

1. Before the migrations are run, displays the sorted list of migrations
2. Before each migration is run, displays the migration which will be run
3. After each migration is run, always displays a completion message. If no changes were made, also displays that as message.

Note that I marked this as "feature", but I'm not sure if it is a new feature, or a "chore" or a "fix"

[vercel]

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

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Jul 30, 2024 8:08am

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 7ced96f. 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 4 targets

• nx affected --targets=lint,test,build,e2e,e2e-ci --base=408eb47e9e80712d53d4f9fa320746c260be7506 --head=7ced96fe214f21c7382ecef6ec97dd345c520469 --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=408eb47e9e80712d53d4f9fa320746c260be7506 --head=7ced96fe214f21c7382ecef6ec97dd345c520469
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[DanielRose]

The e2e tests in multiple-release-branches.test.ts failed sometimes. I investigated the issue, and traced it to the random suffix being created by the uniq helper function. Since it used Math.random directly, the suffix could be shorter or longer, which apparently messes up the internal ordering of the packages.

As fix, I used a helper function based on https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Math/random#getting_a_random_integer_between_two_values to ensure that the random value always has 7 digits.

[JamesHenry]

@DanielRose Thanks so much for figuring out that cause, it's been on my list for a while but it's been rare enough that it's never jumped to the highest priority. I think we can further simplify the implementation details by just using padStart so I've gone ahead and applied that in its own commit so that I can be tracked more easily: #27186

Please could you revert yours and pull that in?

[DanielRose]

@DanielRose Thanks so much for figuring out that cause, it's been on my list for a while but it's been rare enough that it's never jumped to the highest priority. I think we can further simplify the implementation details by just using padStart so I've gone ahead and applied that in its own commit so that I can be tracked more easily: #27186

Please could you revert yours and pull that in?

Rebased on the latest state, excluding the test fixes.

[JamesHenry]

Thanks again, @DanielRose!

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