When 2.4 release is planned: Inspect and merge v2.4 feature branch back to develop

[artntek]

we converted the repo structure from the legacy svn setup (trunk branch with separate release branches) to a regular github workflow (main, develop, and feature branches) in Feb 2024.

main contains the code that is currently released and deployed. develop contains newer code for the next release.

The old master (a.k.a. trunk) branch was converted to a feature branch (feature-5-changes-for-v2.4-from-trunk), since it has changes that are not preset in the 2.3.2 release, but may be needed for 2.4.0.

If so, these should be merged back into develop at that time