feat: add configurable policies

[sebhoerl]

In Île-de-France, it is now possible to add several policies comfortably via configuration. While these are examples, there is a flexible infrastructure behind this code to define additional and custom policies. The current basic idea is that they will modify either the utility estimation and/or the travel disutility while routing. Future iterations may add more components that are modified.

The policies can be activated through the eqasim:policies config group:

<module name="eqasim:policies" >
      <parameterset type="cityTax" >
	      <param name="perimetersPath" value="zone.gpkg" />
	      <param name="policyName" value="myCustomCityTax" />
	      <param name="tax_EUR" value="10.0" />
	      <param name="active" value="true" />
              <param name="personFilter" value="" />
      </parameterset>
      <parameterset type="limitedTrafficZone" >
	      <param name="perimetersPath" value="zone.gpkg" />
	      <param name="policyName" value="myLimitedTrafficZone" />
	      <param name="active" value="true" />
              <param name="personFilter" value="" />
      </parameterset>
      <parameterset type="transitDiscount" >
	      <param name="policyName" value="myTransitDiscount" />
	      <param name="priceFactor" value="1.0" />
	      <param name="active" value="true" />
              <param name="personFilter" value="" />
      </parameterset>
</module>

• City tax: This policy makes agents pay an entry fee when entering a certain zone. Those zones can be defined via the perimetersPath option, which should point to a GPKG file with polygons. The fee that is paid is defined by the tax_EUR option, and it is considered (1) when routing by converting the tax when traversing an entering link into time costs via the cost-beta and the travel-time-beta of the mode parameters. After, (2) the tax is furthermore considered in mode choice by penalizing the choice utility through the cost-beta from the mode parameters. This only applied to car.
• Limited Traffic Zone: This policy makes agents avoid the zones defined in perimetersPath if they don't have the origin or destination of their trip within that zone. Technically, a very high penalty is added to the routing costs when traversing an incoming link.
• Transit discount: This policy allows defining a specific discount level for public transport. The priceFactor will be applied to the base price calculated by the currently selected cost model. Technically, the whole cost term is recalculated and removed from the utility, then the partial cost is added back again.

All policies can be activated or deactivate using the active option. This is especially useful when activating/deactivating policies via the command line.

Furthermore, every policy has a personFilter attribute. If set, the policy applies only to those persons whose person attribute called personFIlter is set to true. If no filter is set, the policy applies to everybody.

Multiple policies of each type can be configured.