Fix undeclared inclusions in CUDA build with GCC on symlinked path
Hi @cheshire Can you please review this PR ? Thank you! I don't think I'm the right person, maybe @MichaelHudgins or @ddunl ? I think @MichaelHudgins or someone from his team is probably best for this one @angerson are you able to take a look at this - or know who best to take a look at it might be?  Hi @angerson Can you please review this PR ? Thank you! Hi @Flamefire Can you please check build failures. Thank you! @gbaned Seems I somehow dropped an `if`. Fixed that and the comment (replacement happens the other way round: Resolved path is replaced by unresolved)   
As an additional safeguard I changed the `inc.replace(cc_topdir_resolved, cc_topdir)` to `cc_topdir + inc[len(cc_topdir_resolved):]` (conditional on `inc.startswith(cc_topdir_resolved)` instead of `cc_topdir_resolved in inc`)

I think this is now as good as it gets and still equivalent to [the patch we actually use](https://github.com/easybuilders/easybuild-easyconfigs/blob/dd300adb91efe3d2dff6c91509e1f0b02deabcb1/easybuild/easyconfigs/t/TensorFlow/TensorFlow-2.1.0_fix-cuda-build.patch) 

I did a quick check and it seems to still work for us. Hi @angerson Can you please review this PR ? Thank you! Hi @angerson Can you please review this PR ? Thank you! Hi @angerson Can you please review this PR ? Thank you! Hi @angerson Can you please review this PR ? Thank you! Hi @angerson Can you please review this PR ? Thank you! Hi @angerson Can you please review this PR ? Thank you! Hi @angerson Can you please review this PR ? Thank you! Hi @angerson Can you please review this PR ? Thank you! Hi @angerson Can you please review this PR ? Thank you! Hi @angerson Can you please review this PR ? Thank you!
When the host compiler (e.g. GCC) is installed in a path being/containing a symlink the CUDA build might fail with `"undeclared inclusion(s)"` to the symlink paths.

This has been partially solved by #56360 which resolves all symlinks in `gcc_host_compiler_path`   
However the compiler referenced there might be a wrapper script (e.g. ccache) which internally eventually forwards the call to the real compiler sitting in a path containing a symlink.
`gcc -v -E - < /dev/null` seems to only return resolved paths while the later invocations include the paths with symlinks leading to the build failure.

The solution employed here is to add the unresolved paths (i.e. the ones with symlinks) in addition to the resolved paths.

Fixes #33975