schema: Redesign to better handle various cases listed here

[christophe-lunarg]

This issue can be used to gather feature new ideas

[christophe-lunarg]

Schema: Improving the handling of feature/property synonyms : #7

[christophe-lunarg]

schema: refactoring to improve checking

Experiment here: #172

• Add extensions and version requirements checking.
  • Eg: VK_KHR_device_group requires VK_KHR_device_group_creation

Schema Implementation:

{
	"type": "object",
	"additionalProperties": false,
	"properties": {
		"VK_KHR_device_group": {
			"type": "object"
		},
		"VK_KHR_device_group_creation": {
			"type": "object"
		}
	},
	"dependentRequired": {
		"VK_KHR_device_group": [ "VK_KHR_device_group_creation" ]
	}
}

JSON file example (if VK_KHR_device_group_creation is removed, then we get an error):

{
    "VK_KHR_device_group": {
      
    },
    "VK_KHR_device_group_creation": {
      
    }  
}

We could implement exclusion of extension vs core version like this:
schema:

{
	"type": "object",
	"additionalProperties": {
		"type": "object",
		"oneOf": [
			{
				"additionalProperties": false,
				"properties": {
					"VK_VERSION_1_1": {
						"type": "object"
					}
				}
			},
			{
				"additionalProperties": false,
				"properties": {
					"VK_KHR_device_group": {
						"type": "object"
					},
					"VK_KHR_device_group_creation": {
						"type": "object"
					}
				},
				"dependentRequired": {
					"VK_KHR_device_group": [ "VK_KHR_device_group_creation" ]
				}
			}
		]
	}
}

JSON files (if VK_VERSION_1_1 is defined, we get errors):

{
	"baseline": {
		"VK_KHR_device_group": {

		},
		"VK_KHR_device_group_creation": {

		}
	}
}

This said, a device profiles will have both the core and the extension defined so we should somehow make this a mode.

[christophe-lunarg]

layer: Allowing to override instance extensions

But this requires big changes in the Vulkan Loader.