Shortcut conflict - be more specific

### Description of the new feature / enhancement

Powertoys shows all shortcut key conflicts. For instance the screenshot below shows 3 conflicts. It specifies which Powertoy shortcut is causing the conflict and links to where this can be changed. But it does not specify what it conflicts with. It instead just gives a generic "system shortcut" label and 'see all windows shortcuts' link which is difficult to browse to find thne conflict at hand.

Additionally, I believe my examples below I are defaults set by PowerToys. It should not by default set shortcuts which conflict with windows

**Recommendation**: Call out the specific system shortcut that is conflicting with the powertoys shortcut.

### Scenario when this would be used?

This would allow me to more efficiently identify which shortcut should take precedence when there is a conflict.

### Supporting information

_No response_

Start by locating the PowerToys shortcut-conflict detection and reporting entry point, then trace how conflicts are classified as generic system shortcuts. The work is done when the conflict view identifies the specific Windows shortcut involved and links to the relevant setting; also verify whether default PowerToys shortcuts conflict with Windows shortcuts.

Written by the indexing model from the issue text.