map mpsd_release with mpsd_spack_fork

Problem:

Currently, the spack_setup.sh script hardcoded the branch of mpsd spack fork to be used. This breaks consistency and reproducibility ( for eg dev-23a and 23b reference to mpsd_v0.19 but when we release 23b we added new packages to mpsd_v0.19 so the dev-23a on disc is non-reproducible)

Solutions:

• keep the mpsd_release somewhere in the branch name of mpsd_spack_fork for eg mpsd_v0.19_dev-23a instead of mpsd_v0.19)
• ensure that for a given release we dont move from one spack version to the other ( we dont have mpsd_v0.19_dev-23a and mpsd_v0.20_dev-23a )
• We update our bash script to use * expansions to identify the correct spack branch to clone