Console/Source issue: "ENOENT: no such file or directory"

## Bug Description

Running the Hermes Debugger via Flipper, the errors that appear in the Console tab are not clickable. The bundle seems to be referenced incorrectly.
When trying to load the bundle via the Sources tab, this appears instead of the bundle code:
"ENOENT: no such file or directory"

(I don't know how to confirm that this issue occurs on JSC or not.) I am able to use the chrome inspector on google chrome in general, so I believe the answer is that it works on JSC. I am only running for IOS so have not run `gradle clean`.

- [ ] I have run `gradle clean` and confirmed this bug does not occur with JSC

Hermes version: 0.8.1
React Native version (if any): 65.1
OS version (if any): macOS 12.0.1
Platform (most likely one of arm64-v8a, armeabi-v7a, x86, x86_64): (Having a hard time finding this information.)

## Steps To Reproduce

1. Run hermes via flipper installation
2. Load your app in a simulator
3. See an error appear in a yellow box in the console tab
4. Click the error link - Nothing happens
5. Go to the Sources tab
6. Choose the folders where the bundle should be, for example: src -> bundle_filename.js
7. See "ENOENT: no such file or directory" instead of the bundle code.

code example:

## The Expected Behavior
Should be able to click an error in the Console tab to jump straight to the error code. Or at least to see the bundle file code in the Source tab by directly visiting the Source tab.