Build troubleshooting for long builds

[AMZN-alexpete]

Change summary

Troubleshooting steps for long builds or builds that freeze or lock up a computer with high CPU core counts

Submission Checklist:

• Descriptive active voice - Do descriptive sentences have a clear subject and action verb?
• Answer the question at hand - Does the documentation answer a what, why, how, or where type of question?
• Consistency - Does the content consistently follow the Style Guide?
• Help the user - Does the documentation show the user something meaningful?

[nicholas-rh]

May or may not be relevant here since they are enabled by default and already mentioned throughout the rest of the documentation, but unity builds are significantly faster (by 2x or more) for me in comparison to non-unity builds.

[AMZN-alexpete]

Considering adding an image showing VS 2022's GUI for setting Maximum number of parallel builds

and maximum concurrent c++ compilations

[lemonade-dm]

We should also mention on Linux that the build could run out of memory and cause OOM killer to run or for certain install cause the machine to reboot.

The cmake --build --j/--parallel option can be used to reduce the number of parallel.

For example on a 12-core 32-GiB machine, the user might want to reduce the number of parallel build jobs to 6 if they are noticing their compile processes are being killed.

cmake --build <build-dir> --j 6 --config profile --target MyProject.GameLauncher -- <generator specific options>

[AMZN-alexpete]

Went ahead and added those VS 2022 menu images, suggestion to use unity builds, and cmake parallel build option.

[lemonade-dm]

Looks good to me

[AMZN-alexpete]

Added @willihay to the review