Add device info to GLES3 shader cache key hash

[bitsawer]

• Fixes OpenGL shader cache is not prefixed with GPU model, causing it to be invalidated when switching GPUs on a project #81150

Adds some extra device info to the shader base cache key hash so that toggling between two different GPU's gives each device their own cache files. I also added the driver version, so driver updates will now also invalidate the cache. On my device, these values are:

GL_VENDOR: NVIDIA Corporation
GL_RENDERER: NVIDIA GeForce GTX 970/PCIe/SSE2
GL_VERSION: 3.3.0 NVIDIA 536.23

[RandomShaper]

I'd like to elaborate on the different caches:

• RenderingDevice (namely, Vulkan):
  1. We're caching SPIR-V representation of shaders so they don't need to be recompiled from GLSL. (GPU-agnostic.)
  2. We're also caching pipelines so they don't need to be created from SPIR-V. (GPU-specific.)
• GL ES 3:
  3. We are caching shader binaries. That's more similar to 2) than 1). It's GPU-specific.

Where I'm getting with this is simply that the file name of the GL ES 3 shader cache could include the GPU device name just as fine as the Vulkan RD one does. For your reference:

godot/drivers/vulkan/rendering_device_vulkan.cpp

Lines 9136 to 9141 in 7e67b49

	pipelines_cache.file_path = "user://vulkan/pipelines";
	pipelines_cache.file_path += "." + context->get_device_name().validate_filename().replace(" ", "_").to_lower();
	if (Engine::get_singleton()->is_editor_hint()) {
	pipelines_cache.file_path += ".editor";
	}
	pipelines_cache.file_path += ".cache";

[bitsawer]

I could add the device name prefix to the cached files too, but I'm not really sure its all that useful compared to the hashing approach where the device name is rolled into the file name hash. I consider it a bit more reliable this way, we don't have to worry about what kind of weird or possibly long name the driver gives us, especially as the user directory+cache directory+file hashes start to get pretty long already and can already approach Windows default path limit of 260. The name format is not really even standardized, most are similar but there are some pretty weird out there.

[RandomShaper]

No big deal. I was just thinking that it could be good for feature parity, but switching GPUs may not be as frequent with GL ES 3.

The path length issues would already be a (very real) matter for Vulkan and should be tackled anyway.

[clayjohn]

Looks good to me.

I'm happy to hash these instead of including in the filename as the filename includes the hash anyway.

[akien-mga]

Thanks!