Remove ch.force_heading and do not allow pass_through for node-based CH

[easbar]

Heading and pass_through does not really work with node-based CH (even though there are cases where it works). Right now there is an extra ch.force_heading parameter that can be set to allow it anyway. Do we need to keep this ? Should pass_through not also be forbidden for node-based CH (unless ch.force_heading is set) ?

On the other hand supporting heading and pass_through for edge-based CH should be possible. Would be nice to have now that we have edge-based CH ?

@devemux86 ?

related: #1697, #1647, #1765

[devemux86]

One of the reasons the flexible mode remains the preferred option in vehicle navigation is because it has features like heading (in degrees), besides the (previous) main benefit of turn restrictions.

If speed mode manages to have also the heading after turn restrictions, that would be awesome. 🙂

[easbar]

And are you currently using heading with speed mode (currently broken and requires ch.force_heading=true) ?

[devemux86]

And are you currently using heading with speed mode (currently broken and requires ch.force_heading=true) ?

No, I use those features only with flexible mode.

[karussell]

Do we need to keep this ?

No

Should pass_through not also be forbidden for node-based CH

Yes

Would be nice to have now that we have edge-based CH ?

Yes :)

[easbar]

For pass_through support with speed mode see #1765, for heading the best you can do atm is using edge-based CH with curbside parameters (see #1697). Sooner or later we should implement heading with edge-based CH.