Improved workaround that solves permission issues for rebuilds

[bedroge]

Instead of recreating all first-level subdirs (as done in #871), this just does an ls on the (removed / non-existing) subdirs. #556 (comment) showed that would solve the issue too, and I tested it in #788 (comment).

The original workaround caused issues for LAMMPS, as it didn't like the empty examples subdir in the installation directory. With the new approach, the installation directory itself is still precreated (and not removed+recreated again by EB), but completely empty. It's cleaner anyway, and also solves the issue for LAMMPS.

[eessi-bot]

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

• architectures: x86_64/generic, x86_64/intel/haswell, x86_64/intel/sapphire_rapids, 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-software, eessi.io-2023.06-compat

[eessi-bot]

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

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

[gpu-bot-ugent]

Instance eessi-bot-vsc-ugent is configured to build for:

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

[eessi-bot]

PR merged! Moved [] to /project/def-users/SHARED/trash_bin/EESSI/software-layer/2025.02.03

[eessi-bot]

PR merged! Moved [] to /project/def-users/SHARED/trash_bin/EESSI/software-layer/2025.02.03

[gpu-bot-ugent]

PR merged! Moved [] to /scratch/gent/vo/002/gvo00211/SHARED/trash_bin/EESSI/software-layer/2025.02.03