VkMemoryAllocateInfo dedicated allocation related VUs are incorrectly validated at vkBind*Memory time

There are certain VUs, such as `VUID-VkMemoryAllocateInfo-pNext-00639` that are validated at `vkBind*Memory` time even though they should be validated in `vkAllocateMemory`, because the VUs belong to `VkMemoryAllocateInfo`.

The validation code even "justifies it" in comments:

```c
// Validate VkExportMemoryAllocateInfo's VUs that can't be checked during vkAllocateMemory
// because they require buffer information.
```

However, that is not really true, certainly not for `VUID-VkMemoryAllocateInfo-pNext-00639`, because buffer information is readily available during `vkAllocateMemory`, as the `VkMemoryDedicatedAllocateInfo` structure includes the buffer/image handles the dedicated allocations are created for.

Locate the validation code that handles VUID-VkMemoryAllocateInfo-pNext-00639 and the related dedicated-allocation checks at vkAllocateMemory and vkBind*Memory. Compare the available VkDedicatedAllocationInfo buffer or image handles at allocation time with the current validation comments. Done means these VkMemoryAllocateInfo VUs are validated at vkAllocateMemory rather than incorrectly deferred to binding.

Written by the indexing model from the issue text.