[TASK] Choose C++ compilers

[RobBryce]

Currently, the Windows build uses Microsoft Visual Studio C++ compiler (2019) and Intel's latest compiler (2022) based on Clang.
Currently, the Linux build uses GCC.

Microsoft and GCC compilers are available on Github for automated builds.
Intel compilers are not available, but there may be a way to use them - if the Intel license lets us.

Clang is available (without Intel's optimizations - in their product now called OneAPI).

The choice of compilation tools impacts:

• the source tree due to slight variations in compiler parsers, compilers, linkers, and library implementations
• final project execution performance
• project runtime (library) dependencies (cstdlib, Intel redistributables, etc.)

Some discussion on preferred compilers may be appropriate before the project is released for general consumption.

[spydmobile]

@RobBryce What more discussion and with whom do you think this needs before we can deal with it? I thought you would simply have to go with clang to be compatible?

[RobBryce]

We currently use GCC for Linux targets.

[BadgerOnABike]

Considering all things seem to be moving to OneAPI and we are having to provide compilers is a move to OneAPI the smart one? (Thinking about this from a user perspective)

[spydmobile]

@RobBryce to simplify these tasks, can you please lay out current compilers against the options you want us to choose from and why they might be a good option.

[BadgerOnABike]

Per our conversations recently. Sounds like Vs '22 is the move in order to support multiple repositories. This may make a number of our decisions for us. Specifically WISE-Developers/Prometheus-EOL-Issues#19

[RobBryce]

Visual Studio 2019 was used on the latest Prometheus builds. I want to roll that ahead to Visual Studio 2022 for a variety of reasons.
We used an old install of the Intel compiler that likely isn't even available for download now. I want to roll that ahead to Intel 2023.

[RobBryce]

Migrating to VS2022 and Intel 2023 per #133