Set device specifically for core diarization clustering
# What does this PR do ?

This PR allows setting a different device (CPU) for the core clustering part of the diarization process so that it doesn't cause GPU OOM errors for long audio files.

**Collection**: ASR

# Changelog 
- Add `device` option to the `diarizer.clustering.parameters` configuration group so that [nemo.collections.asr.parts.utils.speaker_utils.perform_clustering()](https://github.com/NVIDIA/NeMo/blob/e1b3f5e2fe57174863110d3fa47b6c24238ab58e/nemo/collections/asr/parts/utils/speaker_utils.py#L402) (called from [ClusteringDiarizer.diarize()](https://github.com/NVIDIA/NeMo/blob/e1b3f5e2fe57174863110d3fa47b6c24238ab58e/nemo/collections/asr/models/clustering_diarizer.py#L440)) can be executed in the CPU (it's currently hard-coded to run on GPU).
  - This part of the code uses a huge amount of VRAM (over 10GB for an hour of audio) and barely uses the GPU at all, so the performance on CPU doesn't decrease dramatically (processing time increases from 150 seconds on an RTX3090 to 180 seconds on CPU for an hour of audio).
  - This PR is somewhat related to #5681, but instead of setting a device for all processing steps, it allows setting a different device specifically for the function mentioned above.
  - If the new device configuration is not set, it will use the globally set device.
  - The whole reason for this change is supporting audio files over an hour long. It seemed easier to me to run the clustering on CPU than splitting the input audio, diarizing the splits separately and combining the results later. It can surely be done, or there may be a better solution for this, but I don't know enough of Nemo's internals for that yet.

# Before your PR is "Ready for review"
**Pre checks**:
- [x] Make sure you read and followed [Contributor guidelines](https://github.com/NVIDIA/NeMo/blob/main/CONTRIBUTING.md)
- [ ] Did you write any new necessary tests?
- [ ] Did you add or update any necessary documentation?
- [ ] Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
  - [ ] Reviewer: Does the PR have correct import guards for all optional libraries?
  
**PR Type**:
- [x] New Feature
- [ ] Bugfix
- [ ] Documentation

If you haven't finished some of the above items you can still open "Draft" PR.


## Who can review?

Anyone in the community is free to review the PR once the checks have passed. 
[Contributor guidelines](https://github.com/NVIDIA/NeMo/blob/main/CONTRIBUTING.md) contains specific people who can review PRs to various areas.

# Additional Information
* Related to #5681
