Move build toolchain to LLVM 18

[abeltrano]

Type

• Bug fix
• Feature addition
• Feature update
• Documentation
• Build Infrastructure

Side Effects

• Breaking change
• Non-functional change

Background

This change transitions the compiler toolchain from LLVM 17 to LLVM 18, which is not available either as a standard package nor as a GitHub hosted runner image for Ubuntu 23.10 (mantic). It is available for Ubuntu 24.04 (noble) however,

Goals

• Allow the project to be built on a GitHub hosted runner, instead of a self-hosted one.
• Allow running tests not requiring root in GitHub workflows (fix Allow running tests not requiring root in workflows #93).

Technical Details

• Add explicit CMake presets for CI/CD.
• Add hidden CMake presets for Linux compiler toolchains (clang 17, clang 18).
• Enable clang 18 for use in CI/CD, leaving clang 17 as the default for development.
• Change hosted Linux runner to use Ubuntu 24.04 (noble).
• Conditionalize using vcpkg binary caching in build-with-host action, necessary since it is currently implemented in the action script to only work with Windows.
• Add step in build-with-host GitHub action to explicitly install dependencies for the Linux build.
• Update test step in build-with-host GitHub action to only run tests that don't require elevated privileges (root).
• Fix package preset name in build-with-host GitHub action.
• Use fixed preset names for build-specific steps in build-with-host GitHub action.
• Remove self-hosted build from os matrix configuration.
• Enable vcpkg binary caching for both Linux and Windows (previously only configured for Windows).

Test Results

• Test build using the build-with-host action passed.

Reviewer Focus

• None

Future Work

• None

Checklist

• Build target all compiles cleanly.
• clang-format and clang-tidy deltas produced no new output.
• Newly added functions include doxygen-style comment block.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.