Make linking of nvtx3-cpp BUILD_LOCAL_INTERFACE

[KyleFromNVIDIA]

Description

When building as static libraries, CMake tries to export the PRIVATE nvtx3-cpp dependency due to how it handles static library exports. Since nvtx3-cpp is a header-only library, and since cudf's public headers don't depend on it, make it BUILD_LOCAL_INTERFACE to avoid exporting the nvtx3-cpp dependency.

Issue: #15270

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[KyleFromNVIDIA]

/merge

[bdice]

In addition to the Spark failures, this was also seen in the cuSpatial wheel builds: https://github.com/rapidsai/cuspatial/actions/runs/8228471942/job/22497979348

-- Configuring done (27.4s)
CMake Error: install(EXPORT "cudf-exports" ...) includes target "cudf" which requires target "nvtx3-cpp" that is not in any export set.
CMake Error in build/cp310-cp310-manylinux_2_28_aarch64/_deps/cudf-src/cpp/CMakeLists.txt:
  export called with target "cudf" which requires target "nvtx3-cpp" that is
  not in any export set.


-- Generating done (0.1s)
CMake Generate step failed.  Build files cannot be regenerated correctly.

*** CMake configuration failed
error: subprocess-exited-with-error
  
× Building wheel for cuspatial-cu11 (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> See above for output.

[KyleFromNVIDIA]

It looks like cuspatial is building cudf through add_subdirectory() (indirectly through CPM.) With this change, that job should be fixed if it runs again.