Consider using CMake presets

[sharadhr]

This will considerably simplify our CI listings, which have lots of CMake arguments repeated over and over; having it all explicitly listed out in CMake presets that inherit and override one another would make things much more straightforward.

We could have presets for:

• Platforms (Windows, macOS, Ubuntu)
• Toolchains (compilers, build systems (Make, Ninja, MSBuild)
• Environments
  • generator
  • testing
  • samples
  • consumer install: no generation, no tests, no samples

And many more. This will also simplify our version control. I have something set up in my own repository; this could be useful here.

[M2-TE]

With #2458 merged, what else should be added?
As already mentioned there, adding presets for all the environments would result in way too many permutations, since Vulkan-Hpp can be used in multiple ways on even just one toolchain setup.

[sharadhr]

I think this is done and can be closed. I might create another issue to set up toolchain files so we can completely move off defining the toolchain in CI, and just use those toolchain files directly, locally or in CI.