Update spack-packages (#82; cherry-pick upstream Spack package updates); pin py-pandas-datareader

[climbfuji]

Description

This PR updates the submodule pointer for spack-packages for a large number of updates pulled from Spack upstream. See JCSDA/spack-packages#82. One additional package needs to be pinned at the version that is currently being used in spack-stack develop, py-pandas-datareader@0.10.0, because of a py-setuptools incompatibility. This is the same reason why many other packages in configs/common/packages.yaml are pinned to older versions, starting from py-cfparser.

The spack-packages submodule update also brings in a recent bug fix for the hdf5 Fortran interface, see JCSDA/spack-packages#84.

This pull request does not yet update to Python 3.13 - this will be a follow-up pull request that will also undo the py-pandas-datareader pinning.

Dependencies

• Waiting on Cherry-pick upstream Spack package updates spack-packages#82
• Waiting on Bug fix for HDF5: h5open_f failing to re-initialize the Fortran interface spack-packages#84

Issues addressed

Working toward #887

Applications affected

None. No version changes here for the packages we care about and pin in configs/common/packages.yaml.

Systems affected

None

Testing

• CI: Note whether the automatic tests (GitHub actions tests that run automatically for every commit) pass or not
  • GitHub actions CI tests pass
  • GitHub actions CI tests do not pass (provide explanation)
  • GitHub actions CI tests skipped (provide explanation if necessary)
• New tests added: List and describe any new tests added to GitHub actions
  • ...
• Additional testing: Add information on any additional tests conducted
  • Built NEPTUNE environment on my laptop with gcc@14.2.1

Checklist

• This PR addresses one issue/problem/enhancement or has a very good reason for not doing so.
• These changes have been tested on the affected systems and applications.
• All dependency PRs/issues have been resolved and this PR can be merged.
• All necessary updates to the documentation (spack-stack wiki) will be made when this PR is merged

[climbfuji]

The last CI test failed because the runner ran out of disk space. It made it all the way through concretizing and build the environment, then it failed during the deploy step (i.e. from the binary cache). See https://github.com/JCSDA/spack-stack/actions/runs/33795115390/job/100780828622?pr=2114

I'll merge this anyway, followed by the two EPIC updates that don't affect CI. Then I'll try to free up some space on the runner.

[climbfuji]

I removed the old build cache (spack v0.23 = spack-stack versions 1.x) from the CI runner and moved the new one named build-cache-new-spack-v1 to build-cache. I created a symlink from build-cache-new-spack-v1 to build-cache so that the current CI scripts are working. But I'll update those now and create a PR.