Update rubocop, expand pip unsafe packages, preserve swiftlint config

[ydesgagn]

Summary

Routine dependency and configuration maintenance across Ruby, Python, and Swift tooling. Bumps rubocop to its latest patch, broadens the list of NVIDIA/CUDA packages pinned as --unsafe-package for pip-compile (covering both -cu12-suffixed and unsuffixed variants), and enables preserve_config for the swiftlint linter so its repo config is not overwritten.

Key changes:

• Bump rubocop from 1.86.1 to 1.86.2 in Gemfile.lock
• Expand pip-compile --unsafe-package list in config/languages.yaml to cover both -cu12 and unsuffixed NVIDIA/CUDA packages (cuda-toolkit, nvidia-cublas, nvidia-cuda-cupti, nvidia-cuda-nvrtc, nvidia-cuda-runtime, nvidia-cudnn, nvidia-cufft, nvidia-cufile, nvidia-curand, nvidia-cusolver, nvidia-cusparse, nvidia-cusparselt, nvidia-nccl, nvidia-nvjitlink, nvidia-nvshmem, nvidia-nvtx)
• Add preserve_config: true to the swiftlint entry in config/linters.yaml

Types of changes

• Bugfix (fixes an issue)
• New feature (adds functionality)
• Refactoring (improves code without changing functionality)
• Breaking change (incompatible changes)
• Build or security update (updates dependencies, libraries, or security patches)
• Code style or documentation update (formatting, renaming, or documentation changes)
• Other (please describe):

Checklist

• Unit tests added to validate my fix/feature
• I have manually tested my change
• I did not add automation test. Why ?: Configuration and dependency updates only; no behavioral logic to test.
• Database changes requiring migration with downtime or reprocessing of existing data
• The SOUP file lists the risk Level, requirements and verification reasoning associated with each library
• readme.md includes sections on introduction, installation, usage, and contributing
• docs/architecture.md includes sections on the architecture diagram, software units, software of unknown provenance, critical algorithms and risk controls related to PII and security
• Impact on PII, privacy regulations (CCPA/GDPR/PIPEDA), CIS benchmarks or security (availability/confidentiality/integrity); management must be notified