Issue Description:

Optimized (Release) builds that contain `is_escaping_closure` runtime check contain full path of a source file.

The change apparently was introduced in the following commit:

"SIL: Add an is_escaping_closure instruction"
5940796

How to test:

• Create main.swift file with the following contents:

import AppKit; NSAnimationContext.runAnimationGroup({ _ in })

• Compile the file with optimizations and using full path (like Xcode does during builds). E.g.:

$ swiftc -O /Users/username/Desktop/main.swift

• Search for mentions of the file name text in the output file (main)

Expected results:

Optimized (release) build should not have full source paths

Actual results:

Optimized build contains full source path

$ strings main
v16@?0@"NSAnimationContext"8
/Users/username/Desktop/main.swift
runAnimationGroup:

Notes:

The source path is not included in the output if the `is_escaping_closure` check is not used (e.g. in -Ounchecked build or when no such closures are passed to Obj-C in the app)

Other runtime checks might have a similar issue, as I could not pinpoint relevant source changes in the commit mentioned above.