False Positive check_asam_xodr_performance_avoid_redundant_info

[MHoehndorf]

Describe the bug
When checking polynoms for redundant elements we think that it would be better to always set soffset1 to 0.0 and set soffset2 to the length of the first polynom. Otherwise the same two polynoms might be recognized as redundant as well as not redundant, depending on where along the roads these polynoms are located.

To Reproduce

1. Validate the two files in OpenDrive.zip
2. BayArea_wrong_redundant.xodr leads to a redundant elevation element (polynom [6] and [7]). The same two polynoms are also present in the other file (BayArea_no_redundant.xodr), but right at the front of the road. There no error is found in the xodr file.

Expected behavior
No warning should occur for both files