Fix job search: location filtering, keyword quality, anchor filter bypass

Closes #41

- Add RequireKeywordInAnchor per-provider flag (default true); set false for
  ejobs.ro and bestjobs.eu so Stage 2 anchor-text filter is skipped — their
  search URL already filters by relevance server-side
- Update AI system prompts (en + ro) to extract concise job-board-friendly
  keywords (role title + key tech, not abstract concepts) and candidate location
- Propagate location through JobMatchResponse -> CreateJobSearchTokenRequest ->
  JobSearchTokenEntity -> JobSearchSessionEntity
- Add {location} and {location-slug} substitution in HtmlJobSearcher
- Update provider SearchUrlTemplates to include location:
    ejobs.ro:    /locuri-de-munca/{location-slug}?q={keywords}
    bestjobs.eu: /ro/locuri-de-munca-in-{location-slug}?keywords={keywords}
    linkedin.com: ?keywords={keywords}&location={location}
- Three new migrations: AddRequireKeywordInAnchorAndLocation,
  ImproveKeywordsAndAddLocation, AddLocationToProviders

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Apis/cv-matcher-api-models/Requests/CreateJobSearchTokenRequest.cs

@@ -6,4 +6,5 @@ public sealed class CreateJobSearchTokenRequest
     public string Email { get; set; } = string.Empty;
     public string Language { get; set; } = "en";
     public List<string> Keywords { get; set; } = [];
+    public string? Location { get; set; }
 }

Apis/cv-matcher-api-models/Responses/JobMatchResponse.cs

@@ -9,6 +9,7 @@
         public List<string> Recommendations { get; set; } = [];
         public List<string> Evidence { get; set; } = [];
         public List<string> Keywords { get; set; } = [];
+        public string? Location { get; set; }
         public bool Cached { get; set; }
         public string? JobDocumentId { get; set; }
         public string? JobUrl { get; set; }

Apis/cv-matcher-api-models/Settings/JobSearchSettings.cs

@@ -23,4 +23,9 @@ public sealed class JobProviderConfig
     public int MaxResults { get; set; } = 20;
     /// <summary>When true the scraper uses a headless Chromium browser to render JS-heavy pages.</summary>
     public bool UseHeadlessBrowser { get; set; }
+    /// <summary>
+    /// When false, the Stage 2 anchor-text keyword filter is skipped.
+    /// Set to false for providers whose search URL already filters by relevance server-side.
+    /// </summary>
+    public bool RequireKeywordInAnchor { get; set; } = true;
 }