Apply configurable penalty to gates in car profile

[afarber]

Issue

Fixes #6757

The car profile currently whitelists barrier=gate and barrier=lift_gate, making them unconditionally passable when no access tag is present. This is problematic because many real-world gates lack explicit access tags but are not publicly accessible.

This PR applies a configurable time penalty (default 60 seconds) to gates:

• Gates without access tags are routable but incur a 60-second penalty
• Gates with access=yes/permissive/designated bypass the penalty (explicitly open)
• Gates with access=no remain blocked
• Penalty is configurable via profile.barrier_penalties table
• Adds new Gate obstacle type for explicit handling

Tasklist

• CHANGELOG.md entry (How to write a changelog entry)
• update relevant Wiki pages
• add tests (see testing documentation)
• review
• adjust for comments

Requirements / Relations

• Don't penalize gates that have allowed access valhalla/valhalla#3078
• support popular barrier tags valhalla/valhalla#3154
• make absolute barriers passable graphhopper/graphhopper#2345
• no route through access=yes barriers graphhopper/graphhopper#168

[TheMarex]

Hrm, can you say more why you think this is different in OSRM then in all other routing engines you referenced? I actually tried this on openstreetmap.org and the result seems the same between OSRM / Valhalla / Graphhopper.

https://www.openstreetmap.org/directions?engine=fossgis_osrm_car&route=52.551822%2C13.349682%3B52.552262%2C13.349802

The gate in question doesn't have an access tag and default accessibility is assumed for all engines.

This is problematic because many real-world gates lack explicit access tags but are not publicly accessible.

Yeah but the problem is the inverse is also true: There are tons of parking lots that are accessible and protected with barriers. Unfortunately a lot of POIs would need to snap to those parking lots for correct routing (e.g. to the Lidl above). Making these parking lots unaccessible will mean it snaps to the nearest road which can lead to odd results (snap to a backstreet).

A better fix would be to add a penalty in if the access is unclear. Looking at the profile I think we are already doing this? (see obstacles) So I'm not clear in which scenario this was causing wrong results.

[afarber]

@TheMarex updated to use a 60-second penalty instead of blocking. Is this what you had in mind?