Enhance model validation with maximum time horizon check

[merschformann]

Description

Warning

The check for maximum time horizon is technically breaking. The default configured maximum of 1 month (30 days) should not reject any inputs, as the validation only means to detect erroneous inputs.
However, if you are using nextroute for inputs > 1 month planning horizon, we urge you to configure -model.properties.maximumtimehorizon (given in int seconds) to a sufficiently large value. E.g., set it to 5184000 (60 * 24 * 60 * 60), if planning in a 60 day time horizon.

Important

The limit was bumped to 6 months in a follow-up PR to mitigate impact on existing use-cases (#79 ).

Introduced a new option to specify a maximum time horizon for models and added validation to ensure the input data adheres to this constraint.

Changes

• Added MaximumTimeHorizon option in model.go to specify the maximum time horizon for the model.
  • Configure via the -model.properties.maximumtimehorizon option.
  • Value expected in seconds.
  • Default value is 2592000s / 30 days.
• Implemented validateTimeHorizon function in validate.go to check if the input data's time horizon exceeds the specified maximum.
• Modified validate function to include the time horizon validation step.