Sourcegraph follow-up: fix inconsistency when `/` is escaped
Description
It looks like Sourcegraph reads the file path differently when it's fully escaped (including the /). As a result it gives different code intelligence results.
| Fully escaped path (note the browser url) | Correctly escaped path |
|---|---|
 |
 |
This is partly a bug on GitLab's fault. We shouldn't be fully escaping file paths in the fuzzy file finder.