Setting the .net SDK of a project to "net6.0" results in inconsistent controller behavior

Release Type: Official release

Version: 4.1.0.1898

Platform(s): Windows 11

Describe the bug
When the target sdk of the csproj of a project is set to net6.0, its controller detection will be inconsistent with net6.0-windows This caused a lot of trouble when porting an old project.
Basically, if a game is compiled with net6.0, it will detect some controllers (XInput controllers) as GameControllers instead of gamepads and as such, those won't be detected by gamepad functions and will not work with the virtual key binding API.
However if a game is compiled with net6.0-windows specifically, then the input system will behave as intended.

To Reproduce
Steps to reproduce the behavior:

1. Create a project with stride
2. Define the net version as "net6.0" for both the game library and game binary
3. Xbox One and Xbox Series X controllers are detected as GameController and will not work with the virtual input system

Expected behavior
net6.0 should behave the same as net6.0-windows or at least, an error should appear if net6.0-windows specifically is expected on windows for the engine to behave as intended

Start by reproducing the issue with Stride projects targeting net6.0 for both the game library and game binary, then compare the result with net6.0-windows on Windows 11. Inspect the controller detection and virtual input behavior, and consider the issue done when Xbox One and Xbox Series X controllers are consistently recognized as gamepads or an appropriate configuration error is shown.