The mongo pretty printer support files currently hardcode assumptions about what toolchain and standard library were used, but these assumptions do not always hold true. Instead of hardcoding this information, we should let the build system propagate its knowledge of the toolchain and runtime and associated paths into these files, treating the source tree versions as templates, and staging the substituted versions into the installation directory. This will ensure that any given mongodb installation has pretty printer support that correctly reflects the toolchain and runtime library choices. It has the additional benefit of making it possible to use the pretty printers with only an installation of the product, while we currently require a clone of the sources.