check for CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE at enqueue time

See: https://github.com/KhronosGroup/OpenCL-Docs/pull/1493#discussion_r2536306692

Also, refer to discussion in the November 18th teleconference.

Previously, clSetKernelArg described a requirement for a kernel argument set for a pointer to the constant address space to be less than CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE, but this behavior was not tied to any error condition. Additionally, for a multi-device context, the memory object could be valid for some devices in the context, but not for others. Therefore, we decided that this condition should be checked at enqueue time instead, when we know which device will execute the kernel.

Since this is a new error condition, it may need to be added as part of an extension or a new minor OpenCL version.

Start with the linked OpenCL-Docs pull request discussion and the November 18th teleconference notes. Trace the specification text for clSetKernelArg and kernel enqueue errors, then determine whether the new condition belongs in an extension or a new minor OpenCL version; done means the chosen placement and enqueue-time behavior are documented.

Written by the indexing model from the issue text.