feat(pkg): split list 'group' column into 'packageGroups' and 'componentGroups'

[liunan-ms]

Currently the group field on each PackageListResult is the name of the package-group that contains the binary package, or "" if the package isn't in any group. After switching to component-based config, it cannot reflect the component group.

This pull request replaces the single group field on PackageListResult with two independent sorted []string fields: packageGroups (every package-group whose 'packages' list contains the package; always empty for SRPM rows) and componentGroups (every component-group the resolved component belongs to). Both fields are guaranteed non-nil so JSON output is '[]' instead of 'null'.

Updates the table output, JSON schema, CLI help, how-to docs, and unit tests accordingly.

Example output of azldev pkg list --rpm-file <rpm_source_map.json>:

[
...
 {
    "packageName": "fence-agents",
    "type": "srpm",
    "packageGroups": [],
    "componentGroups": [
      "base-packages"
    ],
    "component": "fence-agents",
    "publishChannel": "rpm-base-srpm"
  },
 {
    "packageName": "fence-agents-amt-ws",
    "type": "rpm",
    "packageGroups": [
      "exceptions-packages"
    ],
    "componentGroups": [
      "base-packages"
    ],
    "component": "fence-agents",
    "publishChannel": "rpm-sdk"
  },
  {
    "packageName": "fence-agents-apc",
    "type": "rpm",
    "packageGroups": [],
    "componentGroups": [
      "base-packages"
    ],
    "component": "fence-agents",
    "publishChannel": "rpm-base"
  },
...
]

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

This PR updates azldev pkg list group attribution so packages not belonging to any package-group fall back to their resolved component’s component-group(s), and documents the new behavior.

Changes:

• Add component-group fallback (sorted, comma-joined) for the group field when no package-group match exists, including SRPM rows.
• Add tests covering fallback behavior and package-group precedence.
• Update CLI help and documentation to describe the new group attribution semantics.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
internal/app/azldev/cmds/pkg/list.go	Implements component-group fallback logic via componentGroupLabel, applies it to RPM and SRPM results, and updates help/comments.
internal/app/azldev/cmds/pkg/list_test.go	Adds unit tests validating fallback behavior, sorting/determinism, and package-group precedence, including --rpm-file cases.
docs/user/reference/cli/azldev_package_list.md	Documents the updated meaning of the group column in CLI reference output.
docs/user/how-to/inspect-package-config.md	Updates the Group column description to include the component-group fallback behavior.

[reubeno]

@liunan-ms Is the group actually getting used for anything? Or is it just a diagnostic data point? (I would hope nothing is relying on it for routing correctness.)

[liunan-ms]

@liunan-ms Is the group actually getting used for anything? Or is it just a diagnostic data point? (I would hope nothing is relying on it for routing correctness.)

It's metadata surfaced on azldev package list output to help users understand why a package resolved the way it did (which component-group provides the baseline, which package-group overrides it). Nothing replies on it so this change will not break anything.

[reubeno]

@liunan-ms Is the group actually getting used for anything? Or is it just a diagnostic data point? (I would hope nothing is relying on it for routing correctness.)

It's metadata surfaced on azldev package list output to help users understand why a package resolved the way it did (which component-group provides the baseline, which package-group overrides it). Nothing replies on it so this change will not break anything.

Given that's the case, I'd recommend that we replace 'group' with groups, then, and make it a list? We can clarify whether each group is a component or a package.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

[liunan-ms]

@liunan-ms Is the group actually getting used for anything? Or is it just a diagnostic data point? (I would hope nothing is relying on it for routing correctness.)

It's metadata surfaced on azldev package list output to help users understand why a package resolved the way it did (which component-group provides the baseline, which package-group overrides it). Nothing replies on it so this change will not break anything.

Given that's the case, I'd recommend that we replace 'group' with groups, then, and make it a list? We can clarify whether each group is a component or a package.

Good idea! Instead of having a nested groups with two group lists, I just removed 'group' and add 'packageGroups' and 'componentGroups' lists to indicate the group that the package belongs to.