Follow up on PR #166

List of issues to address once PR #166 is merged:

- Duplicate entries for `mypy` and `pytest` in `Pipfile`
- How do the versions of Python / Conan in `Pipfile` interact with the year-specific versions
- and how does the Conan version set in `packages/conan/settings/version.txt` interact with those?
- better approach to "vendoring" Conan recipes
- update to Conan 2
- clean up packages from CentOS 7 which no longer make sense (libdb4, openjpeg 1)
- get rid of PATH to git-218
- follow up on how to set default C++ ABI (CY2023 requires C++ 11)
- in build-qt.sh don't need special includes of openssl11 -I or -L
- revisit hack for Conan Python sysconfigdata relocation, find solution which works with Conan 2
- build PySide with newer Cmake
- OpenVDB wants to be built with jemalloc
- `build_alembic.sh` first downloads and builds HDF5 but it doesn't seem to configure it in with `-DUSE_HDF5=ON`'
- build GUI for MaterialX
- Optix build and runtime components
- why are `base` Conan packages paying the full price of installing yum packages instead of using the pre-built common image
- better workaround for qtsan_impl.h in QT Conan build
- fix hacks in `packages/conan/recipes/clang/conanfile.py` with hard coded Python versions
- revert to unpaid runner for release builds?
- cppunit unit test failing in Conan build?
- fix clang conan builds (issue with Python Conan package options)

Start by reviewing PR #166 and the follow-up list, then inspect Pipfile, packages/conan/settings/version.txt, build-qt.sh, build_alembic.sh, and packages/conan/recipes/clang/conanfile.py. The issue spans dependency versions, build fixes, packaging, and new components, so a contributor would need to identify a focused task and its relevant tests before defining completion.

Written by the indexing model from the issue text.