Show SolutionConfiguration property when multiple distinct values exist

[Copilot]

Previously, projects that differed only by the SolutionConfiguration property were hard to diagnose because this property was treated as common and elided entirely from the output, even when different values existed across builds.

This change enhances the logger to:

1. Track distinct SolutionConfiguration values across all project builds
2. Display SolutionConfiguration property values when multiple distinct values are detected (instead of eliding them with {elided})
3. Preserve existing behavior when only one SolutionConfiguration value exists

Example

Before: Projects with different SolutionConfiguration values would show no distinguishing properties

Project 3: test.csproj + <SolutionConfiguration = {elided}>
Project 4: test.csproj + <SolutionConfiguration = {elided}>

After: Projects with different SolutionConfiguration values now show the actual values

Project 3: test.csproj + <SolutionConfiguration = Debug>
Project 4: test.csproj + <SolutionConfiguration = Release>

Additional Fix

Fixed a bug in GlobalPropertyValue.CompareTo() method that was comparing Value.CompareTo(Value) instead of Value.CompareTo(other.Value), which could affect property sorting.

Testing

• ✅ Multiple SolutionConfiguration values are displayed with their actual values
• ✅ Single SolutionConfiguration value continues to be elided (preserving existing behavior)
• ✅ Other properties (CurrentSolutionConfigurationContents, etc.) remain unchanged
• ✅ Original example builds continue to work as expected

Fixes #13.

---

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