Add support for Vroom 1.11

[dkastl]

A new version of Vroom was released: https://github.com/VROOM-Project/vroom/releases/tag/v1.11.0

At this stage of the project I would say that we don't need to consider backwards compatibility in case there are relevant changes.

[krashish8]

Yes, we are still in version 0, so anything can change, and thus we don't care about backward compatibility.

[krashish8]

From Vroom v1.11.0 release notes: https://github.com/VROOM-Project/vroom/releases/tag/v1.11.0

Crossing out the entries that require no change, or can be done in the future

Added

• setup key for tasks to refine service time modeling (#358)
• max_tasks key limiting route size at vehicle level (#421, #566)
• Support for custom cost matrices (#415)
• Number of routes in solution summary (#524): Not using this value in SQL
• Implementation for extended SWAP* local search operator (#507): internal
• -l command-line flag for user-provided timeout (#594)
• Ability to start the search from user-defined solution (#376): Not fixing now, leaving for the future. Requires a lot of change.
• Github Actions CI (#436): CI
• Check for libvroom example build in CI (#514): CI

Changed

• vehicle.steps are now used in solving mode (#606): Not fixing now, leaving for the future.
• CI builds now run on Ubuntu 20.04 (#455): CI
• Simplified time window handling logic in TWRoute (#557): Internal

Removed

• Travis CI builds (#436): CI
• Exchange local search operator (#507): internal

Fixed

• "Infeasible route" error while an existing route plan exists (#506): internal
• Break omitted with no other time window (#497): internal
• Biased evaluation in try_job_additions (#572): internal
• Routing error with custom matrix and -g (#561): not using -g flag
• Crash on empty custom matrix (#570)
• Properly allow empty skills arrays (#586)
• Restrict speed_factor in the range (0, 5] (#591)