Request paths with excess bytes are not properly rejected

New path parsing was implemented recently, not officially released yet.

Now we see errors in CTT18. Tool sends paths like:

20 04 24 64 2C 00

According to Vol1 C-1.5 "Segment Definition Hierarchy", these paths are invalid, which is kinda odd because apparanetly the tool expects these paths to be valid.

Anyway, in the implementation, we fail to recognize these paths as invalid. We just stop parsing after the instance ID, ignore the connection point and are happy about it. This is of course wrong and to be fixed with this ticket. CTT18 is expected to suceed then, but we expect further issues when we implemnt diagnostic connection points as the application path EBNF from the spec seems to be wrong/outdated, which requires clarification wfrom the ODVA.