Giordano Salvador

> Minimally, we need the following flows to run in CI: ... - Added `offload_data` to new configs. - Added config `configs/ci-lookup.yaml`.

TBD: `debugview`.

Added `solo/`, `build-only/`, `no-build/`, and `flows/` to `configs/ci/`.

Added `pose_lookup.yaml` and `empty.yaml`.

Added `monado_integration.yaml` and `monado_openxr_app.yaml`.

> Minimally, we need the following flows to run in CI: ... - Updated: `configs/ci/solo/` -> `configs/ci/run-solo.yaml` - Updated: `configs/ci/build-only/` -> `configs/ci/build-only.yaml` - Updated: `configs/ci/no-build/` -> `configs/ci/no-build.yaml` - Removed: `configs/ci/run-solo.yaml:...

> Stuff from stdlib backported to C++-11 (std::optional, std::any) How does this affect our usage of `std=c++17` in `common/common.mk`?

What is the overlap in functionality between runner 2.0 and the changes needed for #126. If the overlap is large, we should merge these issues so that we don't repeat...

We should also evaluate `jam`, which is touted to be portable and simple to use ([Project page](https://www.freetype.org/jam/)).

Should these be managed pointers (e.g., `std::shared_ptr`)?