Release v202211.1

[BenjaminRodenberg]

See precice/precice.github.io#414 for the motivation for this bugfix release.

I'm creating this branch and PR to start collecting relevant changes. Note that it is still unclear if and how we actually would merge these changes into master.

ToDos:

• backport Add missing requirements.txt and venvs for Python tutorials #563

Checklist:

• I added a summary of any user-facing changes (compared to the last release) in the changelog-entries/<PRnumber>.md.
• I will remember to squash-and-merge, providing a useful summary of the changes of this PR.

[MakisH]

Why do we need to change a model parameter in a bugfix release? I know that this was changed in the v202404, but wouldn't this confuse users if v202211.0 and v202211.1 have different values?

[BenjaminRodenberg]

The parameter was not consistent with literature. So I would consider it as a bug that we can also fix in a bugfix release. But let's continue this discussion in #378.

[BenjaminRodenberg]

Additionally, if we want to make sure v202211.1 is future-proof --- respectively even working with Ubuntu 24.04 --- we also could consider backporting #547. This also means that we would need to modify the folder structure of some cases or implement a solution that supports the old structure.

Looks to me like a rabbit hole: Therefore, I would leave things as they are. The user would have to do the venv stuff manually. This is to some degree also consistent with the v202211.1 policy "make sure that your python environment works; we do not even provide the requirements.txt for some cases".