feat: Add advanced location and salary filtering to scanner

[akashgaikwad28]

Code of Conduct

• I agree to follow the Code of Conduct

Existing issues

• I searched existing issues and this hasn't been requested yet

Problem

Currently, the scan.mjs script only filters job postings by title keywords. This leads to a lot of manual noise in the pipeline for users who have strict location requirements (e.g., Remote-only) or salary expectations.

Without these filters, the automated scanner picks up many roles that the user would never consider, forcing them to manually clear their pipeline later.

Proposed solution

I propose adding three new filtering layers to the portal scanner configuration (portals.yml) and implementing them in scan.mjs:

1. Location Toggles: Add remote_only and onsite_only boolean flags.
2. Location Matcher: Add positive and negative keyword lists for specific cities or regions (e.g., 'Pune', 'India', 'EMEA').
3. Salary Range: Add min and max filters for yearly compensation (initially leveraging the Ashby API's structured data).

These changes would allow the scanner to discard irrelevant roles before they ever reach the user's pipeline.

Area

Portal Scanner

[santifer]

Superseded by your own #675 + PR #677, @akashgaikwad28 — the refined proposal in May has clearer scope (configurable salary filtering on top of the existing location filter). Closing this one to keep discussion in one place; let's continue in #675 / #677.

Thanks for iterating on the design.