Allow to set a timeout for searches

[jbruechert]

If supported by the chosen router, it will stop expanding its search interval after the given timeout.

Depends on motis-project/nigiri#68

Workarounds #443 enough to not be a blocker for public hosting.

Let me know if this is generally something you want, and if I should change anything about the implementation.

[felixguendling]

If you want to prevent a malicious user from using CPU resources, this won't be sufficient, because this only "protects" the intermodal API, not the routing API. Make sure to have a whitelist of API endpoints (that doesn't contain the /nigiri or /routing endpoint) in some kind of reverse proxy / load balancer in front of MOTIS. You probably also need to have rate limits in your reverse proxy.

[jbruechert]

Thanks for the hints.

I may add similar things for more endpoints in the future, but for now I'll only allow tested ones.

Right now I am still worried less about malicious users, but more about well-intending ones causing long running tasks by accident.

[jbruechert]

Is there still anything that needs to be done on this?

[felixguendling]

The CI build is all red, so there seem to be errors in the code.

[jbruechert]

The CI builds against nigiri without my changes I think, so that's to be expected