Support ID3D12InfoQueue1 for debug message interception

[kvark]

Is your feature request related to a problem? Please describe.
Routing D3D debug messages to Rust log/console is extremely useful for diagnosing issues and debugging.
The new D3D12 backend of #1602 gets us the "crude" logic of message interception. It hooks into the VEH and manually parses the message to extract the D3D12 part, severity, etc.

Describe the solution you'd like
It may be useful to check for ID3D12InfoQueue1 and use the more specialized hookup instead. This would have to be another code path in parallel with the current VEH. It's unclear what benefit this work will get us, but worth investigating.

See full announcement - https://devblogs.microsoft.com/directx/d3d12-debug-layer-message-callback/

Describe alternatives you've considered
Just keep the current VEH logic.

Additional context
More info from Jessie Natalie:

Unfortunately, this is tied to DXGIDebug.dll, which is not one of the redistributable pieces from the Agility SDK, so it does currently require an insider Win10 or Win11 build

[kvark]

There is also ID3D12InfoQueue that is generally available, but it doesn't let us set a handler. One way to proceed could be to set it up in a way that both periodically polls messages and flushes on destruction... but this can lead to a situation where we aren't exactly sure what causes a particular error.

[Imberflur]

related to #1383