Change postviz trajectories to more detailed foot steps data

Issue, following up on the discussion with @BZoennchen.

I change in !65 (merged) the DataKey of PedestrianFootStepProcessor (see #172 (comment 392984) ).

In the OSM tests the scenarios rimea_04_flow_osm1_[050 | 075 | 100 | 125 | 470]_h were using the PedestrianFootStepProcessor. For now, in the branch, I simply removed the processor from the output file (so the data is currently not available in the output files), in order to avoid exceptions of having the wrong key.

Todo list for this issue, also solves #172 (closed):

• change the postviz.trajectories --> this allows a more detailed visualization
• check out: use tablesaw library? Should be able to read csv data fast and allows data filtering and mapping more easily
• read and cast the new data format in the post visualization
• use (linear) interpolation of the footsteps (inside post visualization) -- when casting to FootStep.class this may already be available there, or using VTrajectory
• adapt the DataKey in all scenarios that have the output file postviz.trajectories set
• if required, adapt the scenarios OSM test scenarios rimea_04_flow_osm1_[050 | 075 | 100 | 125 | 470]_h so that the foot step output is available
• Adapt the (Python) post processing scripts that are currently using the legacy PedestrianFootStepProcessor

We can discuss this again, also if I got the steps right. I am happy to help on this issue, but for now I am first working on !65 (merged) as this has to be merged first, then I ping.

This type of trajectory definition will then (hopefully) also be suitable to insert experimental data into Vadere (the rows do not necessarily have to correspond to foot steps then).