Fix groupBy condition to allow either projectMap or map, not require both

[Copilot]

The groupBy completion check incorrectly required both currentGroupByProjectMap AND currentGroupByMap to be non-null before updating the config. Per the GroupByConfig API design, either projectMap OR map should be provided, not both.

Changes

• Updated condition in ColorConfigContextProvider and SizeConfigContextProvider from && to || logic
• Config now updates when at least one mapping field is initialized (non-null)
• Preserves three-state semantics: null (uninitialized), undefined (deliberately empty), or a value

// Before: Required both fields
currentGroupByProjectMap !== null &&
currentGroupByMap !== null &&

// After: Requires at least one field
(currentGroupByProjectMap !== null || currentGroupByMap !== null) &&

This allows the user to set either a project-global mapping (projectMap) or a custom mapping (map) independently, matching the API contract.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.