Fix and optimize ngen-related image builds

[robertbartel]

Address a few problems and add some optimizations to the ngen worker, calibration worker, partitioner Docker images:

• Move to RockyLinux 9.1 to get default support for GCC 11
  • Needed in particular to work around some current issues in the framework
• Update version of mpich to play nicely with Fortran from GCC 11
• Correct Boost dependency version to be recent enough for current framework requirements (now 1.82.0)
• Modify build stages that build ngen to (typically) do a git pull just before to ensure working on most recent commit for a branch
• Ensuring Docker stack config, which controls the overall build process, establishes the same set of ARG values for related images (ngen, ngen-calibration, etc.) so that things behave as expected/consistently and the build cache is used effectively
• Ensure use of pip's --no-cache-dir option to optimize storage space a bit

[aaraney]

I have one question that should be addressed, but I dont think it necessarily needs to hold this up. Thanks, @robertbartel!

[aaraney]

What are your thoughts on being more explicit here and naming these NGEN_REPO_URL, NGEN_BRANCH, and NGEN_COMMIT instead? If I were looking at a .env file that contained this information and saw REPO_URL I would be a little confused about which repo to specify.