disable using x86_64/amd/zen3 installations when x86_64/amd/zen4 is detected

[boegel]

This makes sense now, since we've caught up in x86_64/amd/zen4, except for installations with the 2022b generation of easyconfigs which are too old for AMD Genoa.

Next to this change, we should also update our Lmod hook to print a clear error why those modules are not available for zen4?

[eessi-bot]

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

• architectures: x86_64/generic, x86_64/intel/haswell, x86_64/intel/skylake_avx512, x86_64/amd/zen2, x86_64/amd/zen3, aarch64/generic, aarch64/neoverse_n1, aarch64/neoverse_v1
• repositories: eessi.io-2023.06-compat, eessi-hpc.org-2023.06-software, eessi-hpc.org-2023.06-compat, eessi.io-2023.06-software

[eessi-bot]

Instance eessi-bot-mc-azure is configured to build for:

• architectures: x86_64/amd/zen4
• repositories: eessi-hpc.org-2023.06-software, eessi-hpc.org-2023.06-compat, eessi.io-2023.06-software, eessi.io-2023.06-compat

[eessi-build-deploy-bot-deucalion]

Instance boegel-bot-deucalion is configured to build for:

• architectures: aarch64/a64fx
• repositories: eessi.io-2023.06-software

[casparvl]

I assume this has to wait for https://gitlab.com/eessi/support/-/issues/37 to have the symlinking for 2022b resolved? Should we put this on draft until then to avoid accidental merge?