Don't initialize device memory allocations in MSan builds
Don't initialize device memory allocations in MSan builds

This allows detecting more potential uses of uninitialized memory in
MemorySanitizer (MSan) builds.

It is the application's responsibility to clear memory allocated by
vkAllocateMemory(), or guarantee that it will be written to before being
read.

Non-MSan builds are unaffected by this change, so that any errors that
are found in the near term don't pose a security risk. A subsequent
change will remove initialization for non-MSan builds as well.

Bug: b/140991626
Change-Id: I079776345c84567875e65e3c390d2b0a29e507db
Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/57890
Kokoro-Result: kokoro <2ac7b1f3fa578934c95181d4272be0d3bca00121@google.com>
Reviewed-by: Alexis Hétu <1c7141772178a7e80858c3db5052b328076f08f4@google.com>
Tested-by: Nicolas Capens <51edc787c30f24c4904e8ffbb5523c3a9f7a451d@google.com>

google/swiftshader,google/swiftshader,google/swiftshader