[Keyboard Manager] Add an option for remapped keys to return to default when a modifier key is pressed

Description of the new feature / enhancement

When keys have been remapped, it throws off remapped shortcuts that use those keys. For example, if you remap S to D and D to S, when clicked they oddly enough do not remap in an infinite loop to each other, but they do remap all associated shortcuts ("save" becomes physical keys Ctl+D). Another example, if I have VolDown mapped to Mute and want Alt+VolDown to do VolUp, then I would have to change the remapped shortcut to Alt+Mute. It creates a big mess because a simple key remapping changes common default shortcuts (like the above illustration, "save" turns into Ctl+D) meaning simple shortcuts have to be remapped to stay default from key changes, and then custom remapped shortcuts don't work because the keys they use are remapped, so you have to remap your remapped shortcuts to the included remapped keys.

Scenario when this would be used?

Beyond the illustrations given above, I run into issues with this scenario because I want to remap PrtScn to be Win+Shift+S [Screen Snip] and Win+PrtScn to be PrtScn [Screenshot]. Because remapped shortcuts act on the remapping of the key involved, when I press Win+PrtScn, Windows receives Win+{Win+Shift+S}. Trying to bypass this creates another problem because a shortcut cannot contain more than two modifiers/3 keys, so I couldn't even create my PrtScn shortcut since Win+Win+Shift+S is not allowed. But that wouldn't work anyway because the key that whole thing is remapped to is PrtScn making it again output Win+Shift+S [Screen Snip]. So, the only way to solve these problems is if there is an option to disable key remappings (or return remapped keys to default) when a modifier key is pressed so that I could have PrtScn remapped AND be able to remap Win+PrtScn without running into a problem. This would also fix problems with nonremapped shortcuts unintentionally changing like Ctl+S in the case of S being remapped.

Read about the whole thing in the issue and comments over at #13341 to see get more insight and see how other default shortcuts like Alt+PrtScn are affected in the whole mess.

Supporting information

I laid my issues out in #13341 thinking that it was a bug when it is just the normal behavior.