🐛 fix(metrics): disable mps for torch metrics

[maxxgx]

📝 Description

Bug: on Mac, the optimal threshold index is out of range.

Torchmetrics returns NaN values when computing the f1 score with device=mps.

Solution: use CPU instead of mps

@ashwinvaidya17 thanks for the suggestion.

✨ Changes

Select what type of change your PR is:

• 🚀 New feature (non-breaking change which adds functionality)
• 🐞 Bug fix (non-breaking change which fixes an issue)
• 🔄 Refactor (non-breaking change which refactors the code base)
• ⚡ Performance improvements
• 🎨 Style changes (code style/formatting)
• 🧪 Tests (adding/modifying tests)
• 📚 Documentation update
• 📦 Build system changes
• 🚧 CI/CD configuration
• 🔧 Chore (general maintenance)
• 🔒 Security update
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)

✅ Checklist

Before you submit your pull request, please make sure you have completed the following steps:

• 📚 I have made the necessary updates to the documentation (if applicable).
• 🧪 I have written tests that support my changes and prove that my fix is effective or my feature works (if applicable).
• 🏷️ My PR title follows conventional commit format.

For more information about code review checklists, see the Code Review Checklist.

[Copilot]

Pull Request Overview

This PR fixes a bug where the optimal threshold index was out of range on Mac by aligning the precision/recall curve shape with thresholds tensor. The issue was caused by torchmetrics using sklearn-style precision/recall format where the last elements are padding values without corresponding thresholds.

• Adds shape alignment check for precision/recall tensors with thresholds
• Removes last element from precision/recall when they have one extra element
• Includes documentation explaining the sklearn precision/recall curve format

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[ashwinvaidya17]

Thanks! Just a super minor thing, we need to update the year range at the top