Automatically rename player process name at runtime to captured application name

[jravi-amd]

What does this PR do?

This PR effectively replaces the functionality in scripts\gfxrecon-replay-renamed.py. Currently supported only on Windows.

How does this work?

On Windows to get the current process name, apps call GetModuleFilename with NULL hModule. This returns the current process name. Graphics drivers often rely on filename returned by this function to apply application-specific optimizations and settings.

On replay during initialization, Microsoft Detours is used to hook GetModuleFilename with our version. So when a graphics driver makes a call to GetModuleFilename(A/W), it gets redirected to our hooked version.

When the replay consumer encounters a process exe name packet in the metadata, we set the original app name in process name override file via a callback from the consumer. The hooked version now returns the original app's exe name instead of gfxrecon-replay.exe.

From the driver's perspective, it receives the original application's process name instead of the replay tool's name. This ensures that application-specific driver optimizations and profiles are correctly applied during replay.

Why do this?

Convenience. Ease of use. Invoking the player as usual, gfxrecon-replay.exe <trace>, should handle process name overrides.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[davidd-lunarg]

The documentation about renaming scripts should be updated to mention the new default behavior for Windows. https://github.com/LunarG/gfxreconstruct/blob/dev/USAGE_desktop_D3D12.md#renaming-scripts

That section should also be copied to USAGE_desktop_Vulkan.md. The new replay flag --disable-process-name-override should be added to the usage documents as well.