Adds max_step param to base_solver

[medha-14]

Description

Fixes #2253

Type of change

Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

• New feature (non-breaking change which adds functionality)
• Optimization (back-end change that speeds up the code)
• Bug fix (non-breaking change which fixes an issue)

Key checklist:

• No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
• All tests pass: $ python -m pytest (or $ nox -s tests)
• The documentation builds: $ python -m pytest --doctest-plus src (or $ nox -s doctests)

You can run integration tests, unit tests, and doctests together at once, using $ nox -s quick.

Further checks:

• Code is commented, particularly in hard-to-understand areas
• Tests added that prove fix is effective or that feature works

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[agriyakhetarpal]

Thanks for starting this! The first part for renaming dt_max to dt_event is largely correct, and you've passed the argument to SciPy's solve_ivp correctly. However, from a first look for the JAX solver, I think this should be passed to jax.experimental.odeint(), noting the difference in the argument name (mxstep vs max_step). I'm much less familiar with the code for the CasadiSolver, so I'll let someone else comment on it.

[agriyakhetarpal]

We should also add an entry to the breaking changes, concerning the rename of dt_max to dt_event.