Allow limiting the used vehicle rentals and parkings

[flaktack]

Summary

Four new parameters are added to RoutingRequest and RoutingResource, which allow limiting the used vehicle rental / parking place by network / tags:

• allowedVehicleRentalNetworks / bannedVehicleRentalNetworks
• requiredVehicleParkingTags / bannedVehicleParkingTags

A few missing parameters are also added to RoutingResource: bikeParkCost, bikeParkTime, carParkCost, carParkTime.

For vehicle rental:

• if there are only banned networks, everything not banned is allowed
• if there are allowed networks, only those may be used
• if there are both allowed and banned networks, banning takes precedence

For vehicle parking -- tags are currently created from OSM tags (fee, supervised, covered, surveillance):

• if requiredVehicleParkingTags is specified, than all tags must be present
• if bannedVehicleParkingTags is specified, than non of the tags may be present

Issue

#3432

Unit tests

☑️

Code style

☑️

Documentation

No changes.

[leonardehrenfried]

We at team stadtnavi have been running this code in production for a few months and it's very useful to us, so I approve it being merged.

I picked up on a duplicate method that can potentially be removed.

[optionsome]

With these current tag options the requiredVehicleParkingTags is probably sufficient. However, I think at some point we might want to allow white listing based on logical or operators too. We could make a separate parameter that expects one of the defined tags to be present but the optimal solution would be to have parameter that would allow to use both "and" and "or" operators. I'm not sure how easy it would be define such format.

[optionsome]

With these current tag options the requiredVehicleParkingTags is probably sufficient. However, I think at some point we might want to allow white listing based on logical or operators too. We could make a separate parameter that expects one of the defined tags to be present but the optimal solution would be to have parameter that would allow to use both "and" and "or" operators. I'm not sure how easy it would be define such format.

We also discussed this today and came to the conclusion that the current implementation is ok for now. If someone has a need for "or" operators we can change the internal model later to support that and implement it in some graphQL API, for example.

[optionsome]

I did purely a code review. I'll probably test at least the vehiclerental parameters soon as I plan to add them to legacy graphql API unless someone else has already done that somewhere/is planning to do it.