Add new GPU workflow

[laraPPr]

to check if missing dependencies for a CUDA build include cpu builds

This action includes an action that is not allowed yet by the EESSI organisation. Could the following action https://github.com/dorny/paths-filter be added to the allowed action.

BUG FIX: It also includes a fix for the existing missing installation check. Currently it fails after running check_missing_installations.sh if their are missing installations. And the workflow is stopped directly after which means the info on which easystack cause the failure is not printed. With this change it is.

[eessi-bot[bot]]

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

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

[eessi-bot[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

[eessi-bot-toprichard[bot]]

Instance rt-Grace-jr is configured to build for:

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

[hvelab]

• Agreed that we don't need the action but is better to do it ourselves
• The other option is to accept -> but security concerns

[laraPPr]

Filter now works see https://github.com/EESSI/software-layer/actions/runs/15493894354/job/43625796367?pr=949 And the check fails as expected see https://github.com/EESSI/software-layer/actions/runs/15493419723/job/43624193008?pr=917

[ocaisa]

@laraPPr I think we can close this as this check is now being done in our EB hooks