Documenting installation FAQ/Troubleshooting

[DinoBektesevic]

As discussed in #449 we have some rather large documentation holes, regarding installation troubleshooting, left.

We should:

1. try to pin the highest cmake versions we can get away with (requires surveying the availability of newer cmake versions amongst the users/available compute resources)
2. write a troubleshooting guide for KBMOD installation process - including finding GPU and the correct Python interpreter in various environments.

This issue is geared more towards figuring out 2 - which should be pretty easy. The kind of problems, of the top of my head, we usually run into:

• nvcc not available
• nvcc is available, but the drivers aren't (i.e. cuda compiler and development packages are installed, but driver and runtimes are not)
• nvcc and drivers exist, but they aren't visible (f.e. managed environments that have several different versions of drivers installed in a non-standard location, or drivers installed in an non-standard location and not visible by default)
• Python discovery fails (f.e. too old CMake, different versions of CMake prioritize different discovery mechanisms/python)