Testing SVM Without the OpenCL 2.x Memory Consistency Model

In OpenCL 3.0 it's theoretically possible to support SVM without supporting the full OpenCL 2.x memory consistency model by reporting a nonzero [CL_DEVICE_SVM_CAPABILITIES](https://bashbaug.github.io/OpenCL-Docs/html/OpenCL_API.html#CL_DEVICE_SVM_CAPABILITIES) but only a very limited [CL_DEVICE_ATOMIC_MEMORY_CAPABILITIES](https://bashbaug.github.io/OpenCL-Docs/html/OpenCL_API.html#CL_DEVICE_ATOMIC_MEMORY_CAPABILITIES) and/or [CL_DEVICE_ATOMIC_FENCE_CAPABILITIES](https://bashbaug.github.io/OpenCL-Docs/html/OpenCL_API.html#CL_DEVICE_ATOMIC_FENCE_CAPABILITIES).

The CTS tests probably do not support this configuration out of the box as no known OpenCL 3.0 implementers are planning to ship this configuration. This issue is to track any observations and known issue regarding this configuration in case a future OpenCL 3.0 implementer does decides to ship this configuration.

This was originally tracked by the item "Evaluate how much can be tested without the OpenCL 2.0 memory consistency model / atomic support" in https://github.com/KhronosGroup/OpenCL-CTS/issues/773.

Start by reading the OpenCL 3.0 CL_DEVICE_SVM_CAPABILITIES, CL_DEVICE_ATOMIC_MEMORY_CAPABILITIES, and CL_DEVICE_ATOMIC_FENCE_CAPABILITIES documentation, then review the related discussion in issue 773. Identify which CTS tests assume the OpenCL 2.x memory consistency model and document or implement the coverage needed for the limited-capability configuration.

Written by the indexing model from the issue text.