Add workaround for RTX HDR driver bug

[cgutman]

Description

This reworks our dummy image handling to avoid triggering a driver bug with 551.61 drivers and RTX HDR enabled. It also provides a small performance improvement for that (uncommon) case of interacting with dummy image textures.

Screenshot

Issues Fixed or Closed

Fixes #2163

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[robbiered]

As a note, a temporary workaround for the repeat crashing is disable HDR in windows.

[ChrisBln2302]

Does this also fix the issue that HDR is not streamed properly when RTX-HDR is enabled for a game?

[RStanbouly]

Nit is relatively minor, otherwise lgtm and it doesn't seem to be failing any checks.

[cgutman]

The minimal workaround turned out to not really be suitable as there were still some major stability issues with this texture upload codepath in the driver, even when it didn't crash by overreading our buffer (the event log was full of GPU error logs from nvlddmkm). I had to resort to a more complex fix, but it at least provides (small) performance benefits for all cases.