feat: Broaden Score Calibration Permissions Create/Update

[bencap]

This pull request introduces new permissions and API endpoints for handling score calibrations in the MaveDB codebase. The main changes include adding a new ADD_CALIBRATION action, updating permission logic to allow broader access to calibration uploads, and requiring users to have email addresses for calibration operations.

Permissions and Access Control

• Introduced the ADD_CALIBRATION action in the Action enum and updated permission checks so any authenticated user can add calibrations to published score sets, while private score sets require owner/contributor/admin access. [1] [2] [3] [4]
• Updated score calibration creation and modification routes to check for ADD_CALIBRATION permission instead of UPDATE, and clarified requirements to include having an email address. [1] [2] [3] [4] [5] [6]
• Changed all score calibration routes to require require_current_user_with_email, ensuring users have verified email addresses for these actions. [1] [2] [3] [4] [5] [6] [7]

Permission Logic Adjustments

• Updated rank-changing logic for calibrations: contributors can always change rank for calibrations on their score set, while owners can only change rank for investigator-provided calibrations.

Minor Fixes and Refactoring

• Fixed import and typing issues in view models and router files, and updated field access in collection update logic for consistency with Pydantic v2. [1] [2] [3]