codegen: Update 'create' criteria

[ncesario-lunarg]

Determine whether or not a command is expected to return a result in a
pointer based on parameter type rather than a hard-coded list of command
names.

Closes #4136.

[ci-tester-lunarg]

CI Vulkan-ValidationLayers build queued with queue ID 18022.

[ci-tester-lunarg]

CI Vulkan-ValidationLayers build # 7365 running.

[ci-tester-lunarg]

CI Vulkan-ValidationLayers build # 7365 passed.

[mikes-lunarg]

Reading the spec a little closer, it looks like this is not the right approach.

vkGetWinrtDisplayNV is not a create call. It should return the same handle when called multiple times with the same arguments, and the returned handle should be one of the VkDisplayKHR handles enumerated by vkGetPhysicalDeviceDisplayPropertiesKHR. Check out ValidationObject::WrapDisplay and Validation::MaybeWrapDisplay to see some of the existing code deal with these handles.

[ncesario-lunarg]

Then perhaps rather than an "allow list," we should have a "block list" of commands that return pointers that should not be wrapped?

[mikes-lunarg]

Sure, we sort of already have that with no_autogen_list which is how it looks like we deal with the existing parts of the API which touch VkDisplayKHR handles (paired with a custom wrapping/unwrapping implementation). It would be really great if we could generalize the VkDisplayKHR wrapping codegen and get rid of the custom implementations since these handles have popped up in a few new extensions now.

[juan-lunarg]

@ncesario-lunarg could you rebase this PR?

It's using the old CI flow which is impacting up the github actions cache.

[juan-lunarg]

Closing due to age / staleness / impacting CI caching

If still valuable please open new PR