Add FMU participants to oscillator tutorial

[uekerman]

v3-compatible replacement of #322
Using my own branch to have write access, instead of #465

Ready for review. Should work with the main branch of the FMI Runner (v0.2.0 will be released before merging here).

Does still ignore #461. I would suggest to do the oscillator after merging here. Otherwise, things get complicated here.

I ran the cases with the precompiled FMU, I did not try to recompile on any other system. @LeonardWilleke compiled the FMU.

The FMU cases give a higher error than the Python implementation (but converge for smaller time step sizes). We still don't understand why exactly IIRC, but this is consistent with the thesis and paper from @LeonardWilleke.

[MakisH]

I tried running this tutorial, but I faced some configuration issue, which should be easy to fix.

In terms of structure, it needs some changes to address #461, but this can happen in a follow-up.

[uekerman]

I can now run FMI2 and FMI3 with the newest version of FMpy 0.3.20 and also all plotting options.

Ready to merge from my perspective.

[MakisH]

I can now also run and plot the results. Almost ready, I just thought we could remove a few potentially unused files and options (see comments).

[MakisH]

Note that if I execute the left with FMI and right with Python, visualizing with

python3 plot-trajectory.py fmi/output/trajectory-Mass-Left.csv TRAJECTORY

gives me this plot:

If I execute the left with Python and right with FMI, visualizing with

python3 plot-trajectory.py python/output/trajectory-Mass-Left.csv TRAJECTORY

gives me this plot:

fmi-fmi gives me the same as python-python:

I have not looked into the details, I am just raising this in case it looks strange.

[uekerman]

The different trajectories look like numerical features to me. Depends on which timestepping methods are used and combined. Playing around with WI, we should be able to remove the instability, but that's beyond this PR.