vkCreateInstance with extensions depending on Vulkan version

Some extensions depend on Vulkan version, e.g. `VK_KHR_surface_protected_capabilities` depends on 1.1.

It is not clear how `vkCreateInstance` should behave.

Layers report this as `VUID-vkCreateInstance-ppEnabledExtensionNames-01388`:

> All required extensions for each extension in the `VkInstanceCreateInfo::ppEnabledExtensionNames` list **must** also be present in that list

But clearly this text only covers extension-extension dependency.

So that makes unclear if it is invalid usage, or should result in `VK_ERROR_EXTENSION_NOT_PRESENT`.

Start by reading the vkCreateInstance requirements around VkInstanceCreateInfo::ppEnabledExtensionNames and VUID-vkCreateInstance-ppEnabledExtensionNames-01388, then compare them with the Vulkan-version dependency example in the issue. Done means the specification clearly states whether this case is invalid usage or returns VK_ERROR_EXTENSION_NOT_PRESENT.

Written by the indexing model from the issue text.