1451 interpolate_simulation_result does not yield consistent timepoints

[reneSchm]

Changes and Information

Please briefly list the changes (main added features, changed items, or corrected bugs) made:

• Replace magic numbers used as tolerances in SystemIntegrator and interpolate_simulation_result by Limits::zero_tolerance.
• Relax default tolerance in interpolate_simulation_result.
• Fix bindings of interpolate_simulation_result, replacing duplicated code by a new bind_interpolate_result_methods function.

If need be, add additional information and what the reviewer should look out for in particular:

• See linked issue for context.
• Please verify that the tolerances and associated calculations make sense.
• There are edge cases that would still "fail", e.g.: Run Systemintegrator with tmax - t0 < 1e-2, and dt or integration set up such that the last step would fail the relative tolerance in the integration step loop (thus tmax - t > 1e-10); then interpolate with the default tolerance.
  • I cannot think of a less convoluted setup, so I think this should be an acceptable solution.

Closes #1451

Merge Request - Guideline Checklist

Please check our git workflow. Use the draft feature if the Pull Request is not yet ready to review.

Checks by code author

• Every addressed issue is linked (use the "Closes #ISSUE" keyword below)
• New code adheres to coding guidelines
• No large data files have been added (files should in sum not exceed 100 KB, avoid PDFs, Word docs, etc.)
• Tests are added for new functionality and a local test run was successful (with and without OpenMP)
• Appropriate documentation within the code (Doxygen) for new functionality has been added in the code
• Appropriate external documentation (ReadTheDocs) for new functionality has been added to the online documentation
• Proper attention to licenses, especially no new third-party software with conflicting license has been added
• (For ABM development) Checked benchmark results and ran and posted a local test above from before and after development to ensure performance is monitored.

Checks by code reviewer(s)

• Corresponding issue(s) is/are linked and addressed
• Code is clean of development artifacts (no deactivated or commented code lines, no debugging printouts, etc.)
• Appropriate unit tests have been added, CI passes, code coverage and performance is acceptable (did not decrease)
• No large data files added in the whole history of commits(files should in sum not exceed 100 KB, avoid PDFs, Word docs, etc.)
• On merge, add 2-5 lines with the changes (main added features, changed items, or corrected bugs) to the merge-commit-message. This can be taken from the briefly-list-the-changes above (best case) or the separate commit messages (worst case).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.29%. Comparing base (54aa7db) to head (e34590e).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1482      +/-   ##
==========================================
- Coverage   97.31%   97.29%   -0.03%     
==========================================
  Files         187      187              
  Lines       16017    16019       +2     
==========================================
- Hits        15587    15585       -2     
- Misses        430      434       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[HenrZu]

Great addition :)
My comments only refer to minor details.