Approximate-location map on aggregated listings (Divar coords)

We captured Divar's privacy-fuzzed coords on RawListing but discarded them for
the listings that need them: unnamed-facility shifts/jobs dropped them (to avoid
piling on the shared placeholder) and applicants had no coordinate field at all.

- Add Lat/Lng to Shift, JobOpening, TalentListing (migration ListingApproxCoords).
- Publish stores the source ad's approx coords on each aggregated listing.
- Detail pages render the map from the listing's own coords (fallback: facility),
  and aggregated coords show as a shaded «محدودهٔ تقریبی» circle (not a precise
  pin) via _NeshanMap data-approx, with a disclaimer. Applicants get a map card
  (they had none) + the page now loads the Neshan key.

Only Divar provides coords; the map needs NeshanMapKey set in admin settings.
Existing rows get coords once reprocessed (RawListing already has them).

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

src/JobsMedical.Web/Models/TalentListing.cs

@@ -59,6 +59,11 @@ public class TalentListing
     [MaxLength(500)]
     public string? SourceUrl { get; set; }
 
+    // APPROXIMATE coords from the source ad (Divar) — an applicant has no facility, so this is the
+    // only location we have. Shown as a «محدودهٔ تقریبی» circle (the area they're available in).
+    public double? Lat { get; set; }
+    public double? Lng { get; set; }
+
     public DateTime CreatedAt { get; set; } = DateTime.UtcNow;
 
     // Transient: distance (km) when "near me" is active. Not persisted.