Investigate removal of Cray compiler wrappers for Narwhal, Blueback, Gaea C5, Gaea C6

[climbfuji]

Is your feature request related to a problem? Please describe.

This is from a conservation with spack developers:

Can you run ls -l /opt/cray/pe/cpe

> ls -l /opt/cray/pe/cpe/
total 1
drwxr-xr-x  2 root root 264 Feb 26  2021 21.03
drwxr-xr-x  2 root root 264 Mar 26  2021 21.04
drwxr-xr-x  2 root root 264 May  3  2021 21.05
drwxr-xr-x. 2 root root 264 Aug 24  2021 21.09
drwxr-xr-x  2 root root 264 Feb 16  2022 22.03
drwxr-xr-x  2 root root 264 Aug 22  2022 22.09
drwxr-xr-x  2 root root 264 Oct 27  2022 22.11
lrwxrwxrwx  1 root root   5 Aug 22  2022 default -> 22.09

Ok by what I have anything newer than 21.10 is supposed to support using the compilers without cc/CC/ftn, and Spack should be detecting yours as 22.09. Is your 22.09 not letting you use the compilers without cc/CC/ftn?
...
Interestingly, the two things I had to do to get fully functional spack environments were (a) tell spack that the external cray-mpich package uses the cray wrappers (+wrappers) and change the Python package to always apply the cray-rpath patch, i.e. remove the when condition.

Describe the solution you'd like
Move away from Cray compiler wrappers were possible

Additional context
See https://spackpm.slack.com/archives/C5W7NKZJT/p1694393880262699

[climbfuji]

In #1266, I was able to switch the GNU compiler setup on Narwhal to not use the Cray compiler wrappers in preparation for spack-stack-1.8.0. Moving this to "in progress" with the target for implementation across all Cray systems and compilers in spack-stack-1.9.0.