libosrm: global namespace pollution #2940
Description
In #2938 (comment) a user reported name clashes when trying to use libosrm.
Turns out our typedefs.hpp header is not namespaced, but we install it to the user's include dir.
This not only pollutes the user's global namespace but also is prone to name clashes as reported in the ticket linked above when trying to use / embed libosrm.
cc @MoKob I'm tagging this 6.0 already since it's a breaking libosrm API change.