Fix incorrect computation of pointer size
CTS always fills the array of pointers with a stride of 64-bits.
So, for 32-bits applications, each two 32-bits has one valid pointer
to instance of bottom-level acceleration structure.
To correct this the pointer size should be calculated as
sizeof(VkDeviceOrHostAddressConstKHR::hostAddress) for host built
top-level acceleration structure and
sizeof(VkDeviceOrHostAddressConstKHR::deviceAddress) for device built
top-level acceleration structure.
VK-GL-CTS issue: 3084
Components: Vulkan
Affects:
dEQP-VK.ray*instances_aop*
Change-Id: I8c412a5a5d2ce3f1f687795768d6d83ad4913892