Add Celeritas cmake command wrappers for downstream code

[sethrj]

This follow-on to #1673 restores and automatically exposes celeritas_-prefixed wrappers for downstream applications:

• This allows us to someday not distribute CudaRdcUtils if it's not applicable, or if the capabilities get built into cmake
• It makes it more obvious to downstream users where the command is coming from
• It improves configure performance if CUDA or VecGeom are disabled

[github-actions]

Test summary

 4 291 files   6 548 suites   13m 38s ⏱️
 1 782 tests  1 771 ✅ 11 💤 0 ❌
22 842 runs  22 759 ✅ 83 💤 0 ❌

Results for commit dfdd793.

♻️ This comment has been updated with latest results.

[stognini]

Since cuda_rdc_target_link_libraries was refactored to celeritas_target_link_libraries, is the include(CudaRdcUtils) going to be updated to something like include(CeleritasUtils)?

[sethrj]

Since cuda_rdc_target_link_libraries was refactored to celeritas_target_link_libraries, is the include(CudaRdcUtils) going to be updated to something like include(CeleritasUtils)?

cuda_rdc_target_link_libraries still exists, but now it's preferred for downstream libraries to call celeritas_target_link_libraries for the reasons describe in the header. To simplify things for users, and to be more like other libraries (e.g., Clang and ROOT both provide helper macros without you having to include a separate file) users will no longer have to include anything.

[stognini]

e.g., Clang and ROOT both provide helper macros without you having to include a separate file

Oh I see, that is what you meant when you mentioned not distribute CudaRdcUtils if it's not applicable. Thanks

[sethrj]

@esseivaju I'm going to add another quick follow-on to fix the perfetto installation. @pcanal could you give this a quick lookover?

[pcanal]

LGTM.