[Specification] Missing sanity requirements for VkImageFormatProperties

There are missing requirements regarding the VkImageFormatProperties from vkGetPhysicalDeviceImageFormatProperties

• relationship of tiling and usage and VkFormatProperties feature flags (so far only defined for 0 flag; and only in a Note)
• incompatible formats and usages (e.g. depth format and color attachment usage)
• VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT and VK_IMAGE_TILING_LINEAR should have maxArrayLayers at least 6 (not 1)
• VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT should return same number for maxExtent.width and maxExtent.height
• Generally should respect image creation VUs, e.g.:
  • VK_FORMAT_UNDEFINED should always return unsupported
  • VK_IMAGE_TYPE_3D should return only maxArrayLayers of 1
  • VK_IMAGE_CREATE_CUBE_COMPATIBLE_BIT and 1D and 3D type should return unsupported
  • if usage has X_ATTACHMENT the returned maxExtent must be at least VkPhysicalDeviceLimits::maxFramebufferWidth\Height
• should respect enabled\disabled features? E.g. should return unsupported if VK_IMAGE_CREATE_SPARSE_BINDING_BIT and sparseBinding is disabled?