Merge v4.2.2 from 'latest' into 'release-v5.0.0'

[jemrobinson]

:white_check_mark: Checklist

• [x] You have given your pull request a meaningful title (e.g. Enable foobar integration rather than 515 foobar).
• [x] You are targeting the appropriate branch. If you're not certain which one this is, it should be develop.
• [x] Your branch is up-to-date with the target branch (it probably was when you started, but it may have changed since then).

:vertical_traffic_light: Depends on

n/a

:arrow_heading_up: Summary

Merge changes to ensure that develop can be cleanly merged into latest when required.

:closed_umbrella: Related issues

n/a

:microscope: Tests

n/a

[JimMadge]

I changed the target branch to the release branch.

[jemrobinson]

@JimMadge : sure - although really this should have been done into develop immediately after we released v4.2.2.

[github-actions[bot]]

Coverage report

This PR does not seem to contain any modification to coverable code.

[JimMadge]

Probably. I think the branches have diverged enough now that the merge will probably be mostly to discard changes from 4.2.2.

[jemrobinson]

Yes, it is - although with changes to docs it was worth manually checking that the same changes had made it into the v5 docs too.

[jemrobinson]

39 commits to make 0 changes to files :)