Acorn updates; go fetcher

[AlexanderRichert-NOAA]

Summary

This PR:

• adds oneAPI 2024.2.1 on Acorn
• adds util/fetch_go_deps.py
• adds platform-specific logic for setup.sh (for loading modules, etc.)

Testing

Successfully built unified env on Acorn.

Applications affected

UWM, GW, GSI

Systems affected

go fetcher can be used wherever, and site maintainers may choose to add site-specific logic in setup.sh; otherwise no expected impacts to platforms other than Acorn

Dependencies

none

Issue(s) addressed

Fixes #1615
Fixes #1616
Fixes #1597
Addresses #1574 by adding workaround for Acorn

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.

[AlexanderRichert-NOAA]

FYI @DavidHuber-NOAA

[AlexanderRichert-NOAA]

@climbfuji I was toying with the idea of tweaking the compiler filtering logic for spack stack create env so that I can just give it a list of the compiler specs that I want to keep. The invocation would be something like:

spack stack create env --template unified-dev --name test --site acorn --compiler [email protected] --keep-compilers [email protected],[email protected]

and the default would go back to the original, i.e., no compiler filtering. In any case, I want a better way to specify exactly what I want so that I don't have, say, intel creeping into my oneapi environment.

If that sounds good I can do either in this PR or in a separate one.

[climbfuji]

@climbfuji I was toying with the idea of tweaking the compiler filtering logic for spack stack create env so that I can just give it a list of the compiler specs that I want to keep. The invocation would be something like:

spack stack create env --template unified-dev --name test --site acorn --compiler [email protected] --keep-compilers [email protected],[email protected]

and the default would go back to the original, i.e., no compiler filtering. In any case, I want a better way to specify exactly what I want so that I don't have, say, intel creeping into my oneapi environment.

If that sounds good I can do either in this PR or in a separate one.

A separate PR is a good idea imo

[climbfuji]

#1618 was merged, please resolve the conflicts and mark this PR as ready/add reviewers and I will look at it. Thanks!

[climbfuji]

That hostname is very unfortunate. I can totally see other platforms using something like this, too ... but for now we don't have any other one.

[AlexanderRichert-NOAA]

We can use hostname --fqdn. I'll be out the next couple days but I'll update this when I get the chance. With that it can be alogin*ncep.noaa.gov or something like that.

[climbfuji]

We can add that when we need it - for now we're ok.