Add CI log grouping for align-deps output

[vivekjm]

Summary

Adds CI log grouping around align-deps output so runs over larger workspaces are easier to scan in GitHub Actions and Azure DevOps.

This keeps local output unchanged and only opens a group when a package actually writes log output, avoiding empty groups for packages with no changes.

Fixes #2906.

Testing

• git diff --check
• yarn workspace @rnx-kit/align-deps format
• PATH="/Users/vivek/.cache/codex-runtimes/codex-primary-runtime/dependencies/node/bin:$PATH" yarn workspace @rnx-kit/align-deps lint
• PATH="/Users/vivek/.cache/codex-runtimes/codex-primary-runtime/dependencies/node/bin:$PATH" yarn workspace @rnx-kit/align-deps build --dependencies
• PATH="/Users/vivek/.cache/codex-runtimes/codex-primary-runtime/dependencies/node/bin:$PATH" yarn workspace @rnx-kit/align-deps test

[tido64]

Thanks for your contribution! I've left some comments.

[tido64]

Nit: Type can be inferred

Suggested change

	env: Env = process.env
	env = process.env

[vivekjm]

Good call, thanks. I removed the explicit env type and let TypeScript infer it from the default value.

[tido64]

We should use encodeURI instead:

Suggested change

	start: `::group::${escapeGitHubCommand(title)}`,
	start: `::group::${encodeURI(title)}`,

[vivekjm]

Done. I switched the GitHub Actions group title handling to use encodeURI here.

[tido64]

Can we always return start/end functions instead?

  const { beginGroup, endGroup } = getGroupMarkers();
  const errors = manifests.reduce((errors, manifest) => {
    try {
      beginGroup(manifest);
      ...
    } finally {
      endGroup(manifest);
    }

[vivekjm]

Updated this to expose beginGroup/endGroup through getGroupMarkers. I also moved the call site behind a small helper so the CLI loop stays readable.

[tido64]

I don't think this is correct. This will always start a group even though we don't know if anything will be logged yet. When no changes are needed, nothing should be logged.

[vivekjm]

Agreed. I changed the implementation so the group starts lazily on the first log/warn/error for that manifest. If nothing is logged, no group markers are emitted.