Add Resend List Emails API with POST endpoint for recipient-based status lookup

[Copilot]

Adds a recipient-indexed Resend email status lookup API, replacing the resend_id-dependent approach so delivery status works for all historical emails. The resend-list endpoint is exposed as POST (not GET) to avoid 414/400 URL length failures with large volunteer lists.

What does the PR do?

Backend (services/volunteers_service.py)

• list_all_resend_emails() — fetches Resend List Emails API (paginated, up to 10 pages), builds a recipient-keyed index, caches in Redis at resend:all_emails_index (300s TTL)
• Cache is invalidated after send_volunteer_message() and send_email_to_address() succeed
• Empty results are cached (avoids hammering Resend on zero-email accounts)
• Page fetch errors skip caching entirely rather than serving partial stale data

API (api/volunteers/volunteers_views.py)

• POST /api/admin/emails/resend-list — auth-protected endpoint; accepts { "emails": ["a@b.com", ...] } JSON body
• emails field supports both array and comma-separated string
• Switched from GET + query string to POST + JSON body to handle large volunteer lists without hitting URL length limits

POST /api/admin/emails/resend-list
Authorization: ******
Content-Type: application/json

{ "emails": ["volunteer@example.com", "another@example.com"] }

Type of change

• Breaking Change
• Bug Fix
• New Feature

Linked Issue

Make sure you have

• Pulled from the default branch
• Documented your changes
• Linked the Issue
• Appointed a reviewer (if any)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.