Merge master back into develop

Explanation of changes

Merges master, containing the new release, back into develop and adds a missing entry in the changelog.

---

Merge checklist

See also merge request guidelines

• Merge request has been reviewed and approved by a project maintainer.
• Merge request contains a clear description of the proposed changes and the issue it addresses.
• Merge request made onto appropriate branch (develop for most MRs).
• New code is fully tested.
• New code is documented and docstrings use numpydoc format.
• Changelog has been updated (when applicable).
• CI pipelines pass
  • black code-formatting passes (gitlab-ci),
  • test suite passes (gitlab-ci),
  • no degradation in code-coverage (codacy),
  • no (serious) new pylint code quality issues introduced (codacy),
  • documentation builds successfully (CI and readthedocs),
  • windows tests pass (manually triggered by maintainers before merging).

---

For reference, the issues workflow is described in the contribution guidelines.