Create GitHub runner docker images for newer Ubuntus

[kwabenantim]

Summary
Create images with dependency versions for:

• Ubuntu 22.10 Kinetic Kudu End of Life
• Ubuntu 23.04 Lunar Lobster
• Ubuntu 23.10 Mantic Minotaur

Tasks

• Build docker image for chaste/runner:kinetic.portability-dev.
• Build docker image for chaste/runner:lunar.portability-dev.
• Build docker image for chaste/runner:mantic.portability-dev.
• Modify boost modulefiles in old portability images to set FindBoost.cmake variables.
• Fix workflows to use FindBoost.cmake variables from modulefiles.
• Write developer documentation on building and testing new dependency versions (https://github.com/Chaste/developer_wiki/wiki/Portability-Testing)
• Fix cvector errors.

PRs

• Modify portabilities for new Ubuntus #205
• Docker runners for new Ubuntus dependency-modules#60
• Fix module tests for system images dependency-modules#61
• Boost config for system images dependency-modules#62
• Update boost config dependency-modules#63

Related Issues

• Test Chaste compatibility with newer Ubuntus #198

[kwabenantim]

Currently, system images don't configure correctly because -DBoost_NO_BOOST_CMAKE and -DBoost_NO_SYSTEM_PATHS are set directly in CI workflows. Moving the options into the modulefiles will allow images to set them ON and OFF as required.

[kwabenantim]

Getting maybe-uninitialized errors with GCC 13.2.0 on Ubuntu 23.10 Mantic Minotaur: https://github.com/Chaste/dependency-modules/actions/runs/7539367160/job/20521728238

[mirams]

Worth a look to see if the compiler is correct, sometimes it is and sometimes it isn't for these sort of warnings. Probably don't want to disable that warning globally anyway, it is a useful one!

[kwabenantim]

Worth a look to see if the compiler is correct, sometimes it is and sometimes it isn't for these sort of warnings. Probably don't want to disable that warning globally anyway, it is a useful one!

Thanks @mirams. It is probably an issue with boost configuration in this case.

[kwabenantim]

It turns out boost is configuring properly. The same error occurs in the base Ubuntu 23.10 Mantic Minotaur image without the modulefiles.

[kwabenantim]

All portabilities pass except for the new ones - Lunar (gcc 12) and Mantic (gcc 13).

The configure step completes okay, but the build step throws maybe-uninitialized errors.

https://github.com/Chaste/Chaste/actions/runs/7623994326

[MILeach]

@fcooper8472 to investigate c vector errors