Use GitHub action to install Vulkan SDK

[bashbaug]

The OpenCL SDK CI currently downloads and installs the Vulkan SDK somewhat manually:

OpenCL-SDK/.github/workflows/presubmit.yml

Lines 432 to 433 in aa33d56

	VULKAN_SDK_URL: https://sdk.lunarg.com/sdk/download/1.3.261.1/windows/VulkanSDK-1.3.261.1-Installer.exe
	VULKAN_SDK: C:/VulkanSDK/1.3.261.1

OpenCL-SDK/.github/workflows/presubmit.yml

Lines 475 to 485 in aa33d56

	- name: Install samples dependencies
	run: |
	Invoke-WebRequest ${env:VULKAN_SDK_URL} -OutFile vulkan-sdk-installer.exe
	.\vulkan-sdk-installer.exe --accept-licenses --default-answer --confirm-command install com.lunarg.vulkan.32bit
	Remove-Item vulkan-sdk-installer.exe
	if ('${{ matrix.BIN }}' -eq 'x64')
	{
	echo "Vulkan_LIB_DIR=$env:VULKAN_SDK/Lib" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append
	} else {
	echo "Vulkan_LIB_DIR=$env:VULKAN_SDK/Lib32" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append
	}

We should use a GitHub action to do this instead, which should be much simpler and more reliable. For example:

https://github.com/jakoch/install-vulkan-sdk-action

[MathiasMagnus]

If the concern over increasing supply chain surface doesn't outweigh the benefit of offloading the responsibility of the installer interface changing or handling arm64 installs then it should be a simple change to use a 3rd party component to install the Vulkan SDK. The linked action seems pretty featureful. A slightly lighter version with less customizability would be to just issue winget install -e --id KhronosGroup.VulkanSDK. Both seem to do the trick with the action potentially yielding faster CI runs at the expense of moderately larger supply chain (NodeJS vs. Winget).

Edit: @bashbaug do take a peek at your Discord for a DM ;)