[Bug]: ImmoScout24 job fails with "Real estate type not found: haus-mit-garage-kaufen" when "Garage" filter is enabled

[wasserfreak]

Bug Description

When creating an ImmoScout24 job with a search URL that includes the "Garage"
filter (under Ausstattung/features) for a house purchase search, the job
fails during initialization. The same search URL with the "Garage" filter
disabled works without any issue.

Steps to Reproduce

1. On immobilienscout24.de, create a search for houses for sale ("Haus kaufen")
2. Enable the "Garage" filter under Ausstattung
3. Copy the resulting search URL
4. Paste the URL into a new Fredy job for provider "Immoscout"
5. Run/trigger the job

Expected Behavior

The job runs and returns matching listings, as it does for the same search
without the Garage filter.

Actual Behavior

The job fails immediately with the following error:

​ [2026-07-27 09:09:38] ERROR: Error: Real estate type not found: haus-mit-garage-kaufen at convertWebToMobile (file:///fredy/lib/services/immoscout/immoscout-web-translator.js:222:15) at Module.init (file:///fredy/lib/provider/immoscout.js:228:16) at executeJob (file:///fredy/lib/services/jobs/jobExecutionService.js:181:27) at process.processTicksAndRejections (node:internal/process/task_queues:103:5) at async runSingle (file:///fredy/lib/services/jobs/jobExecutionService.js:130:5) ​

Screenshots / Logs

No response

Environment

• Fredy version/image tag: v23.1.0 - Deployment: Docker (docker compose) - Provider: Immoscout24

Additional Context

Workaround

Disabling the "Garage" filter on the same search avoids the error.

Suspected cause (unverified)

It looks like ImmoScout24 encodes "Garage" as part of the real-estate-type
path segment itself (haus-mit-garage-kaufen) rather than as a separate
query parameter, when it's combined with a house-for-sale search. The
mapping table in convertWebToMobile (immoscout-web-translator.js)
presumably doesn't have an entry for this combined segment, only for the
base haus-kaufen.