[FEA]: consider to use `nv_exec_check_disable` for most of libcu++ algorithms / functors

[miscco]

Is this a duplicate?

• [X] I confirmed there appear to be no duplicate issues for this request and that I agree to the Code of Conduct

Area

libcu++

Is your feature request related to a problem? Please describe.

Currently we mark everything as __host__ __device__ which would disallow __device__ or __host__ only functions even if they are perfectly fine and only ever used in the right execution context.

We should add nv_exec_check_disable to most of those features that take a function object so that we do not bother users too much with it

Describe the solution you'd like

Add the appropriate macro consistently in libcu++

Describe alternatives you've considered

No response

Additional context

No response

[jrhemstad]

This would be a good opportunity to introduce a unified macro we can use across all CCCL libs.

[jrhemstad]

@gevtushenko ran into this most recently in mdspan with providing a custom accessor that was __device__ only.