[DOC]: Update contributing guide to include information on how to use cmake presets

[jrhemstad]

Is this a duplicate?

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

Is this for new documentation, or an update to existing docs?

New

Describe the incorrect/future/missing documentation

As a maintainer and contributor to CCCL, I want to know how to conveniently and easily build and execute CCCL's tests.

The current contributor guide provides information on using the ci/build_* and ci/test_* scripts, but it should also provide guidance on using the cmake presets. This should include information on using the cmake presets directly on the command line, as well as using the cmake vscode extension in our devcontainers.

The desired structure would be something like:

## Building and Testing

CCCL components are header-only libraries. This means there isn't a traditional build process for the library itself. However, before submitting contributions, it's a good idea to build and run tests.

There are multiple options for building and running our tests, which you choose depends on your preferences and if you are using [CCCL's DevContainers](.devcontainer/README.md) (highly recommended!). 

### Using Manual Build Scripts
#### Build
// existing stuff
#### Test
// existing stuff

### Using CMake Presets
// 1-2 sentence description of what cmake presets are w/ link
#### Using CMake Presets via Command Line
// Show code block using presets via cli

#### Using CMake Presets via VSCode GUI (Recommended when using DevContainers)
// Show how to configure presets in cmake extension in devcontainer
// Include screenshots

If this is a correction, please provide a link to the incorrect documentation. If this is a new documentation request, please link to where you have looked.

No response