clCreateImage disallows creating mimapped CL_DEPTH images, but CTS and Intel NEO ignore it.

[The OpenCL spec on clCreateImage states:](https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_API.html#clCreateImage)

```
Mip-mapped images cannot be created for [CL_MEM_OBJECT_IMAGE1D_BUFFER](https://registry.khronos.org/OpenCL/specs/3.0-unified/html/OpenCL_API.html#CL_MEM_OBJECT_IMAGE1D_BUFFER) images, depth images or multi-sampled (i.e. msaa) images.
```

However the CTS currently doesn't seem to exclude this case and tries to create a CL_DEPTH image with mipmaps. I was also testing with Intel NEO and it seems it successfully creates such an image and hence passing the test.

What should we do about it?

Start with the cited clCreateImage specification text and compare it with the CTS case that creates mip-mapped CL_DEPTH images. Check the reported Intel NEO behavior, then determine whether the specification or the CTS needs clarification or correction. Done means the expected behavior and the required follow-up are explicitly decided.

Written by the indexing model from the issue text.