Cleanup naming discrepancy in renderer backend (sometimes Vulkan, sometimes without)

[PowerOfNames]

Aurora

Decide on a naming schema for general and specific renderer objects. Should classes/files directly using vulkan encoorporate that in their name for more clarity and potential fixing in the future, or never contain vulkan.

If Vulkan wouldn't be enough, Aurora would not add another backend, but rather using an existing RHI (like NVRHI) to replace Vulkan -> it should technically not exist a VK namespace OR Vulkan in any of the names, and it should be clear that all renderer specifics use Vulkan.

The only thing that needs to be cared of is, that none of the public API should expose Vulkan specifics out to the Aurora-users.

-> Remove the VK namespace and Vulkan from any of the class- and file names for clearance (and shorter names lol)

[PowerOfNames]

Edit:

On second thought, the namespace and naming convention should be kept (adding Vulkan to the missing parts) - this way, we can properly abstract away Vulkan specific code, which should not be exposed to users of Aurora.

Current idea:

Have a very thin abstraction for the main Aurora objects that get exposed.