replace Z3 dependency for PyTorch-2.1.2-foss-2023a.eb

[trz42]

A recent change to the easyconfig PyTorch-2.1.2-foss-2023a.eb (see easybuilders/easybuild-easyconfigs#20050) lets the check for missing installations fail, for example, see
https://github.com/EESSI/software-layer/actions/runs/8268611041/job/22621916438?pr=500#step:4:2130

This PR adds a hook that attempts to replace the dependency for Z3 with the version that was used before (with suffix -Python-3.11.3).

CI should not fail anymore. However, running eb with --missing prints messages that the dependency has been replaced, but the renamed dependency is then not listed anymore. Running with --dry-run does show the renamed dependency. Not sure if this behaviour is expected or not.

[eessi-bot-aws]

Instance eessi-bot-mc-aws is configured to build:

• arch x86_64/generic for repo eessi-hpc.org-2023.06-compat
• arch x86_64/generic for repo eessi-hpc.org-2023.06-software
• arch x86_64/generic for repo eessi.io-2023.06-compat
• arch x86_64/generic for repo eessi.io-2023.06-software
• arch x86_64/intel/haswell for repo eessi-hpc.org-2023.06-compat
• arch x86_64/intel/haswell for repo eessi-hpc.org-2023.06-software
• arch x86_64/intel/haswell for repo eessi.io-2023.06-compat
• arch x86_64/intel/haswell for repo eessi.io-2023.06-software
• arch x86_64/intel/skylake_avx512 for repo eessi-hpc.org-2023.06-compat
• arch x86_64/intel/skylake_avx512 for repo eessi-hpc.org-2023.06-software
• arch x86_64/intel/skylake_avx512 for repo eessi.io-2023.06-compat
• arch x86_64/intel/skylake_avx512 for repo eessi.io-2023.06-software
• arch x86_64/amd/zen2 for repo eessi-hpc.org-2023.06-compat
• arch x86_64/amd/zen2 for repo eessi-hpc.org-2023.06-software
• arch x86_64/amd/zen2 for repo eessi.io-2023.06-compat
• arch x86_64/amd/zen2 for repo eessi.io-2023.06-software
• arch x86_64/amd/zen3 for repo eessi-hpc.org-2023.06-compat
• arch x86_64/amd/zen3 for repo eessi-hpc.org-2023.06-software
• arch x86_64/amd/zen3 for repo eessi.io-2023.06-compat
• arch x86_64/amd/zen3 for repo eessi.io-2023.06-software
• arch aarch64/generic for repo eessi-hpc.org-2023.06-compat
• arch aarch64/generic for repo eessi-hpc.org-2023.06-software
• arch aarch64/generic for repo eessi.io-2023.06-compat
• arch aarch64/generic for repo eessi.io-2023.06-software
• arch aarch64/neoverse_n1 for repo eessi-hpc.org-2023.06-compat
• arch aarch64/neoverse_n1 for repo eessi-hpc.org-2023.06-software
• arch aarch64/neoverse_n1 for repo eessi.io-2023.06-compat
• arch aarch64/neoverse_n1 for repo eessi.io-2023.06-software
• arch aarch64/neoverse_v1 for repo eessi-hpc.org-2023.06-compat
• arch aarch64/neoverse_v1 for repo eessi-hpc.org-2023.06-software
• arch aarch64/neoverse_v1 for repo eessi.io-2023.06-compat
• arch aarch64/neoverse_v1 for repo eessi.io-2023.06-software

[casparvl]

Hm, this is really due to the difference between the set of EasyConfigs used to build and the set of EasyConfig used when running --missing.

For the build, because PyTorch is in https://github.com/EESSI/software-layer/blob/2023.06-software.eessi.io/easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-4.9.0-2023a.yml , we run EasyBuild version 4.9.0. For the --missing, we run the EasyConfigs from the develop branch, since @ocaisa 's #486 .

Make me wonder if this actually makes sense. There was a good reason for it, as it allowed us to strip a lot of --from-pr's, and enforce that EasyConfigs should be merged. However, it is fundamentally inconsistent to use different versions of the EasyConfig in the --missing check.

I need to think about what the best way is to proceed. This PR could work as a workaround. We could also explicitly install Z3 without the Python prefix (i.e. new naming), to make the --missing check pass (it doesn't really hurt to install that). Not sure what's preferable...

[boegel]

I would do the latter (installing Z3 without Python versionsuffix) in short term.

The idea is to switch to using --from-commit when that's ready anyway, and then many of the issues shouldn't present themselves anymore?

[ocaisa]

I'd be with @boegel here, the easy (and harmless) fix is to just install the new Z3

[trz42]

Obsolete after installing Z3 (#502)