Applicants: 1→N contact methods with types (phone/email/Instagram/Telegram/Bale/site)

- ContactMethod entity (Type + Value + SortOrder) 1→N on TalentListing (+ migration).
- Parser extracts ALL contacts: multiple phones + landlines, email, and
  socials (Instagram/Telegram/Bale/WhatsApp/website) via URLs and Persian
  keyword cues; primary Phone kept for cards.
- ContactInfo helper: per-type label/icon/clickable href (tel:/mailto:/t.me/…).
- Ingestion attaches contacts to each (fanned-out) talent listing; manual
  Review re-parses to attach them + the admin-typed phone.
- Talent details renders the full contact list as buttons; falls back to the
  single phone, then the Divar source link.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

src/JobsMedical.Web/Models/ContactMethod.cs

@@ -0,0 +1,23 @@
+using System.ComponentModel.DataAnnotations;
+
+namespace JobsMedical.Web.Models;
+
+/// <summary>
+/// One contact channel for an applicant («آماده به کار») listing. A listing can carry several —
+/// e.g. three phones + an email + an Instagram page. <see cref="Value"/> holds the raw handle /
+/// number / address; <see cref="Type"/> decides how it's linked (tel:, mailto:, t.me/…, etc.).
+/// </summary>
+public class ContactMethod
+{
+    public int Id { get; set; }
+
+    public int TalentListingId { get; set; }
+    public TalentListing TalentListing { get; set; } = null!;
+
+    public ContactType Type { get; set; }
+
+    [Required, MaxLength(250)]
+    public string Value { get; set; } = "";
+
+    public int SortOrder { get; set; }
+}