make input_configuration pricing defaults more user friendly

[bricegnichols]

Instead of a switch to turn on or off distance pricing, have a setting that defines the planned start year of distance pricing, e.g. 2025. So, if the run year >= that year, distance pricing will be applied. This might help catch instances of forgetting to apply prices in the correct years if we can assume a consistent implementation year.