Allow custom user-defined data in `get_spirv_key` for shader permutation generation

[Przemog1]

Description

The nbl::this_example::builtin::build::get_spirv_key function should allow custom, user-defined data.

Description of the related problem

Currently, there is no reasonable way to create shader permutations based on data outside of the limit or features structs. For example, such functionality would be needed in the 28_FFTBloom example: https://github.com/Devsh-Graphics-Programming/Nabla-Examples-and-Tests/blob/e5d5ae2ca9137a6966d00aa039f3e6dae7c23fb9/28_FFTBloom/main.cpp#L183-L207.

[devshgraphicsprogramming]

Seems that custom named permutation structs would be needed, same as deviceCaps is generated by the NSC toolchain.

[devshgraphicsprogramming]

The signature of the get_spirv_key could just be

template<core::StringLiteral Key, typename... AdditionalPermutationStructs> requires (is_trivial_v<AdditionalPermutationStructs> && ...)
std::string_view get_spirv_key<Key>(limits, features, const AdditionalPermutationStructs&...);

We'd "just" have to settle on a C++20/23 reflection library which is forward compatible with future C++26 reflection

Then for each member of AdditionalPermutationStructs we'd add (.memberName_<value>) also maybe insert __ as the struct name first to prevent ambiguities/collisions.