Failing CUDA sanity check of CUDA-Samples 12.1 CUDA 12.1.1

[laraPPr]

We saw failing sanity check in #1190.

  >> CUDA sanity check summary report:
  >> Number of CUDA files checked: 128
  >> Number of files missing one or more CUDA Compute Capabilities: 12 (ignored: 0, fails: 12)
  >> Number of files with device code for more CUDA Compute Capabilities than requested: 17
  >> (not running with --cuda-sanity-check-strict, so not considered failures)
  >> Number of files missing PTX code for the highest configured CUDA Compute Capability: 35 (ignored: 0, fails: 35)
  >> You may consider rerunning with --cuda-sanity-check-accept-ptx-as-devcode to accept suitable PTX code instead of device code.
  >> You may consider running with --cuda-sanity-check-accept-missing-ptx to accept binaries missing PTX code for the highest configured CUDA Compute Capability.
  >> See build log for detailed lists of files not passing the CUDA Sanity Check

So we disabled the sanity check with --cuda-sanity-check-accept-missing-ptx:True for foss/2023a.

JSC implemented a fix for recent version of CUDA-Samples see easybuilders/easybuild-easyconfigs#23651.