[skip ci] Add ifx at TOSS5

[mathomp4]

Description

Adds a oneapi-ifx stack at NAS on TOSS5

Dependencies

None

Issues addressed

None

Applications affected

None

Systems affected

NAS TOSS5

Testing

• CI: Note whether the automatic tests (GitHub actions tests that run automatically for every commit) pass or not
  • GitHub actions CI tests pass
  • GitHub actions CI tests do not pass (provide explanation)
  • GitHub actions CI tests skipped (provide explanation if necessary)
• New tests added: List and describe any new tests added to GitHub actions
  • ...
• Additional testing: Add information on any additional tests conducted
  • ...

Checklist

• This PR addresses one issue/problem/enhancement or has a very good reason for not doing so.
• These changes have been tested on the affected systems and applications.
• All dependency PRs/issues have been resolved and this PR can be merged.
• All necessary updates to the documentation (spack-stack wiki) will be made when this PR is merged

skip-checks: true

[mathomp4]

This works for me at NAS. Apologies to @climbfuji for not adding the [skip ci] in my initial PR opening. I tried adding them ex post facto to see if it triggers when the branch is updated. That said, I'll avoid pressing "Update branch" for now since @climbfuji might want to do things in a specific order.

[climbfuji]

This works for me at NAS. Apologies to @climbfuji for not adding the [skip ci] in my initial PR opening. I tried adding them ex post facto to see if it triggers when the branch is updated. That said, I'll avoid pressing "Update branch" for now since @climbfuji might want to do things in a specific order.

Everything that needed to be merged is in; we can merge this and create the release branches afterwards.

[mathomp4]

This works for me at NAS. Apologies to @climbfuji for not adding the [skip ci] in my initial PR opening. I tried adding them ex post facto to see if it triggers when the branch is updated. That said, I'll avoid pressing "Update branch" for now since @climbfuji might want to do things in a specific order.

Everything that needed to be merged is in; we can merge this and create the release branches afterwards.

Sounds good.

And, of course, I can't update the wiki until we have a v2.1 wiki 🙂