[WIP] Add Intel Sapphire Rapids support to archdetect

[bedroge]

Should not be merged before the stack is complete (I guess?).

Tested on AWS:

[bedroge@x86-64-intel-srapids-node3 software-layer]$ ./init/eessi_archdetect.sh cpupath
x86_64/intel/sapphire_rapids

[bedroge@x86-64-intel-srapids-node3 software-layer]$ ./init/eessi_archdetect.sh -a cpupath
x86_64/intel/sapphire_rapids:x86_64/intel/skylake_avx512:x86_64/intel/haswell:x86_64/generic

I've based the detection on two flags found at https://en.wikipedia.org/wiki/Sapphire_Rapids#CPU. Only using avx512-bf16 would not work though, as it was apparently also available in Cooper Lake (but not its successor), see https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html. Also used amx_tile, which should only be available in Sapphire Rapids and later. Perhaps we could even stick to only that one?

[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

[boegel]

I've based the detection on two flags found at https://en.wikipedia.org/wiki/Sapphire_Rapids#CPU. Only using avx512-bf16 would not work though, as it was apparently also available in Cooper Lake (but not its successor), see https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html. Also used amx_tile, which should only be available in Sapphire Rapids and later. Perhaps we could even stick to only that one?

I don't see the downside in checking for both, so makes sense as is for me

[bedroge]

Do we want to change this to sapphirerapids to be consistent with archspec's naming? It would require a symlink (or complete rebuild...) for the already built packages.

Suggested change

	"x86_64/intel/sapphire_rapids" "GenuineIntel" "avx2 fma avx512f avx512bw avx512cd avx512dq avx512vl avx512_bf16 amx_tile" # Intel Sapphire/Emerald Rapids
	"x86_64/intel/sapphirerapids" "GenuineIntel" "avx2 fma avx512f avx512bw avx512cd avx512dq avx512vl avx512_bf16 amx_tile" # Intel Sapphire/Emerald Rapids

[boegel]

Ugh... No strong preference, I guess.

A rebuild just to remove a _ is a bit extreme, of course.

A symlink is easy, but less clean.

I'm not sure we should 100% stick to the archspec naming, although that does sort of make sense I guess.

In short: ask others for input here ;)

[ocaisa]

I think some of our CI will break if the names don't align...but we also need #485 to make sure archspec is up to date for architectures