Issue Description:

As Jeff Johnson described in his blog post, compiling Swift code containing fatalError leads to the absolute file bath being embedded into the binary – even for release builds. This could potentially leak sensitive information about the developer/system that compiled the binary.

I suggest that the absolute file path should be stripped for release builds, similar how it is done for preconditionFailure, with the exception that fatalError should not be optimized in -Ounchecked builds.