Building O3DE on VS2022 slower than VS2019 depending on configuration

[amzn-changml]

Describe the bug If a build that previously was running with code and artifacts from VC142 (Visual Studio 2019's C++ compiler) is switched to VC143 (Visual Studio 2022's compiler) on the same machine, there may be unexpectedly longer build times. This is inconsistent from build to build, however.

Assets required O3DE code base from the Development branch

Steps to reproduce Steps to reproduce the behavior:

1. Configure and build O3DE using VC142 on VS2019
2. Finish the build
3. Configure and build the same source using VC143 on VS2022, using default configurations
4. Finish the build
5. Note a slower overall build time

Expected behavior The same or faster build time on VS2022 as VS2019

Actual behavior A slower overall build time (observed 15% slower in some cases)

Screenshots/Video VS2019 Incremental Profile Build: https://jenkins.build.o3de.org/blue/organizations/jenkins/O3DE_periodic-incremental-daily/detail/development/113/pipeline/1054 (1h 16m 16s)

VS2022 Incremental Profile Build: https://jenkins.build.o3de.org/blue/organizations/jenkins/O3DE/detail/development/3164/pipeline/378 (1h 40m 32s)

Found in Branch Development

Desktop/Device (please complete the following information):

• Device: PC
• OS: Windows/Windows Server
• Version 10/2019
• CPU Intel Xeon Platinum 8000 and AMD Ryzen 5900x
• GPU N/A
• Memory 32 GB (Intel) and 64 GB (AMD)

Additional context Core/Memory usage ratio from cl.exe/link.exe is also under investigation. Some reports on MS's side here: https://developercommunity.visualstudio.com/t/c-compile-in-vs-2022-is-much-slower-than-in-vs2019/1680228