[FEA]: Change default CMake options from developer usecase to install-only / packaging usecase

[alliepiper]

Is this a duplicate?

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

Area

General CCCL

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

The current default CMake options configure a build that is generally targeted at developers by enabling tests, etc. Now that we have presets designed for development and CI, the default CMake options no longer matter for these usecases.

I propose that we change the default options to be more convenient for users and packagers by only generating install rules when configuring CCCL as a top-level project.

The add_subdirectory usage of CCCL by users (e.g. submodules, CPM, fetch_content, etc) would not change, and would continue to provide the appropriate CMake targets for use in downstream projects.

Describe the solution you'd like

1. Audit the current CMake options and change their defaults to only generate install rules.
2. Ensure that any changed options are explicitly specified with the intended value in the CMake presets.
3. Add CI job that configures CCCL with default options and only enables the CCCL install tests to verify that the default installation is functional.

Describe alternatives you've considered

No response

Additional context

No response

[alliepiper]

#1945 added an install cmake preset that effectively provides the same functionality as this request through cmake --preset install.