refactor: use React useId() hook for filter component IDs

[afonsojramos]

Summary

• Replace hardcoded id props in filter components with React's useId() hook
• Ensures SSR-safe unique IDs following React best practices
• Extracted from feat: migrate from Electron to Tauri v2 #2479 per review feedback

Changes

• ReasonFilter: id="filter-reasons" -> useId()
• StateFilter: id="filter-state" -> useId()
• SubjectTypeFilter: id="filter-subject-type" -> useId()
• UserTypeFilter: id="filter-user-types" -> useId()

Test plan

• All existing tests pass
• Snapshots updated to reflect new ID format

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[afonsojramos]

After opening this PR, I did some thinking, instead of trusting the linter, and I think that to be honest, useId() doesn't really make sense here. Since this is client-only, no SSR, and useId() was designed to solve hydration mismatch issues, specifically, between server and client.

[setchy]

Makes sense, good pickup