Use estimated travel distances instead of euclidian distance

[Hussein-Mahfouz]

Introduces a new feature to account for detour factors and decay rates when calculating travel distances. These travel distances are used in estimating feasible zones, and in plotting actual vs reported distances. Related to #79

Key changes:

Utility Function Updates:

• src/acbm/assigning/utils.py: Added _adjust_distance function and updated zones_to_time_matrix to include detour and decay adjustments when calculting travel distance from euclidean distances. To check parameters, see this interactive wolfram alpha plot
• src/acbm/assigning/feasible_zones_primary.py: Updated get_possible_zones to include detour_factor and decay_rate parameters and adjusted the travel time matrix accordingly.
• src/acbm/validating/utils.py: Updated calculate_od_distances to include the detour and decay adjustments.

Configuration Updates:

• config/base.toml: Added detour_factor and decay_rate parameters under the new [feasible_assignment] section.
• src/acbm/config.py: Introduced FeasibleAssignmentParams class and added it to the Config class.

Script Updates:

• scripts/3.1_assign_primary_feasible_zones.py: Updated the get_possible_zones function to pass detour_factor and decay_rate to the travel time matrix and filtering functions.
• scripts/3.3_assign_facility_all.py: Updated the plot_scatter_actual_reported function to use the new parameters when plotting. The distance is calculated from the euclidian distance.
• scripts/4_validation.py: Added detour_factor and decay_rate parameters to the distance validation plots.