Streamline the checks for missing installations

[ocaisa]

This only checks the easystack files that are using the latest releases of EasyBuild (since this is our policy and there is little point in checking older easystacks over and over)

[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-build-deploy-bot-deucalion]

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

• architectures: aarch64/a64fx
• repositories: 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

[trz42]

Looks fine mostly. A few suggestions for the script only_latest_easystacks.sh. Might also be worthwhile to put curly brackets around all variable names.

The one rebuild easystack file that was moved, it was not necessary for this PR, just something you noted?

[trz42]

If you source init/eessi_defaults you don't have to change the version here later.

[ocaisa]

I wanted this to be configurable in CI via setting the envvar

[ocaisa]

The value here is actually set in the CI configuration, this is only here as a fall back in case someone explicitly calls this script for some reason

[ocaisa]

@trz42 One rebuild easystack was moved because it was in the wrong location, it should have been under the accel subdirectory, the other had an inconsistent date stamp (just happened to see it)