Metadata Creation Uses spack --config-scope Scopes

[CodeGat]

Closes #356

Background

Currently, if we install a package that uses a custom spack --config-scope, the metadata creation logic doesn't know about this, leading to certain models binaries that use restricted directories (like ACCESS-ESM1.6) to not be able to be md5 hashed.

The PR

• Update the get_data_from_deployment.py script to take a --config-scopes arg, which loads the appropriate spack-config/custom/cd scopes.

Testing

Tested via the docker image: ghcr.io/access-nri/build-ci-upstream:rocky-v1.1-2026.02.000, in which I copied the script and ran:

spack env activate --create e
spack install --add access-esm1p6
./get_data_from_deployment.py \
  --environment /opt/environments/e \
  --deployment-name access-esm1p6 \
  --packages um7 \
  --config-scopes ukmo-restricted-scope

and it successfully generated md5 hashes of the um7 package binaries.

[aidanheerdegen]

Sweet-as bro