libkvikio conda packages are built with INTERFACE_COMPILE_DEFINITIONS that require CUDA 12.2 for cuFile Stream APIs

[bdice]

This issue describes a build failure seen in cudf's devcontainers with CUDA 12.0 when using the libkvikio conda packages that are now built with CUDA 12.2, as of #328. The build failures look like this:

  In file included from /home/coder/.conda/envs/rapids/include/kvikio/defaults.hpp:26,
                   from /home/coder/.conda/envs/rapids/include/kvikio/buffer.hpp:23,
                   from /home/coder/.conda/envs/rapids/include/kvikio/file_handle.hpp:31,
                   from /home/coder/cudf/cpp/src/io/utilities/datasource.cpp:26:
  /home/coder/.conda/envs/rapids/include/kvikio/shim/cufile.hpp:59:12: error: 'cuFileReadAsync' was not declared in this scope; did you mean 'cuFileRead'?
     59 |   decltype(cuFileReadAsync)* ReadAsync{nullptr};
        |            ^~~~~~~~~~~~~~~
        |            cuFileRead

The libkvikio conda packages contain this in lib/cmake/kvikio/kvikio-targets.cmake:

set_target_properties(kvikio::kvikio PROPERTIES
  INTERFACE_COMPILE_DEFINITIONS "KVIKIO_CUFILE_FOUND;KVIKIO_CUFILE_BATCH_API_FOUND;KVIKIO_CUFILE_STREAM_API_FOUND"
  INTERFACE_COMPILE_FEATURES "cxx_std_17"
  INTERFACE_INCLUDE_DIRECTORIES "${_IMPORT_PREFIX}/include"
  INTERFACE_LINK_LIBRARIES "Threads::Threads;CUDA::toolkit;cufile::cuFile_interface;dl"
)

In other words, the INTERFACE_COMPILE_DEFINITIONS are being set based on the packages available during the libkvikio conda build, which might not be the same packages/versions as when libkvikio is actually being used. Because we built libkvikio with CUDA 12.2 and then tried to use it with CUDA 12.0 devcontainers, the build failed to find the cuFile Stream APIs that were introduced in CUDA 12.2.

I am opening a PR that proposes to defer these definitions until the call to find_package, which will use the exact cuFile features present (if cuFile is available at all) when building a package like cudf that depends on kvikio.