[FIX] Install dxvk and vkd3d on new prefixes if enabled

[Etaash-mathamsetty]

Use the following Checklist if you have changed something on the Backend or Frontend:

• Tested the feature and it's working on a current and clean install.
• Tested the main App features and they are still working on a current and clean install. (Login, Install, Play, Uninstall, Move games, etc.)
• Created / Updated Tests (If necessary)
• Created / Updated documentation (If necessary)

[CommandMC]

Do we consider DXVK/VKD3D to be part of a "complete prefix"? As in, should we consider a prefix to be unusable if those tools aren't installed while they're enabled in the settings?

• If we do, I'd say this should happen in verifyWinePrefix instead
• If we don't, runWineCommand shouldn't do this at all & the caller should instead decide when it wants to take care of these operations

I'm conflicted here, although I'd favor doing it in verifyWinePrefix

[Etaash-mathamsetty]

Do we consider DXVK/VKD3D to be part of a "complete prefix"? As in, should we consider a prefix to be unusable if those tools aren't installed while they're enabled in the settings?

* If we do, I'd say this should happen in `verifyWinePrefix` instead

* If we don't, `runWineCommand` shouldn't do this at all & the caller should instead decide when it wants to take care of these operations

I'm conflicted here, although I'd favor doing it in verifyWinePrefix

1. we can't do it in verifyWinePrefix because we should not need the gameSettings just to verify the wine prefix
2. The caller cannot do it because that would cause lots of code duplication and the prefix might not exist yet in many places.
3. This is supposed to be a simple bug fix so that I don't have to keep turning on and off dxvk every time I download a game and try to run it, it's just one click play now :)

[CommandMC]

verifyWinePrefix already takes GameSettings, it just happens to not look at anything but the Wine version & prefix. If you do want to force DXVK/VKD3D to be installed if they're enabled, installing them in the function preparing the prefix would make more sense to me (rather than the function that "just" runs a given Wine command)

On (3):
DXVK and VKD3D are already auto-installed on launch for all games that are ran with Wine (using one function for all storefronts), see

HeroicGamesLauncher/src/backend/launcher.ts

Lines 229 to 237 in 297bf24

	// If DXVK/VKD3D installation is enabled, install it
	if (gameSettings.wineVersion.type === 'wine') {
	if (gameSettings.autoInstallDxvk) {
	await DXVK.installRemove(gameSettings, 'dxvk', 'backup')
	}
	if (gameSettings.autoInstallVkd3d) {
	await DXVK.installRemove(gameSettings, 'vkd3d', 'backup')
	}
	}

Testing this locally, it works exactly as designed (it always tries to install those components, even if they're already installed, but that's fine)

[Etaash-mathamsetty]

seems like prepareWineLaunch wasn't run for sideloads