"Reveal in Explorer View" misbehaves with out-of-workspace files

**Current behavior:** When the user selects "Reveal in Explorer View" from the context menu of a non-workspace file, the file is not always revealed in the Explorer View (for any reasonable definition of the word "reveal"). **Expected behavior:** When the user selects "Reveal in Explorer View" from the context menu of a file, the file is revealed in the Explorer View. <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions --> <!-- 🔎 Search existing issues to avoid creating duplicates. --> <!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ --> <!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --> <!-- 🔧 Launch with `code --disable-extensions` to check. --> Does this issue occur when all extensions are disabled?: Yes <!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --> <!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. --> - VS Code Version: 1.73.1 (and source code reviewed from the current main branch 7f65f0213caa93be075fedb6ce87885a4ce56eab) - OS Version: Linux x64 Steps to Reproduce: 1. Open a folder or workspace, and open some files from there (e.g., foo.c and foo.h). 2. Open a file which is *not* in the folder or workspace (e.g., /usr/include/stdio.h). 3. While a workspace file (e.g., foo.h) is active, right-click the non-workspace file and select "Reveal in Explorer View":  4. Observe how the non-workspace file is *…