### Godot version

4.0.beta17.mono.official

### System information

Windows 10

### Issue description

As the title says, the log output is needlessly deep into internals (screenshot here: https://github.com/godotengine/godot/pull/71943#issuecomment-1415809223), but the actual issue is that double clicking the log entry doesn't jump to the source file but attempts to open the source-generator generated file instead:
![grafik](https://user-images.githubusercontent.com/8841352/216606839-039fc4c7-4645-4c30-96a1-1f49c59d489c.png)


### Steps to reproduce

Print debug statements from a c# file, and try to double click the log entry in the editor.

### Minimal reproduction project

If required i can create one
ERR_FAIL_COND_V(!is_session_active() || p_frame < 0, false);
	Array msg;
	msg.push_back(p_frame);
	_put_msg("get_stack_frame_vars", msg, debugging_thread_id);
	return true;
}
void ScriptEditorDebugger::set_live_debugging(bool p_enable) {
	live_debug = p_enable;
}
void ScriptEditorDebugger::_live_edit_set() {
	if (!is_session_active() || !editor_remote_tree) {
		return;
	}
	TreeItem *ti = editor_remote_tree->get_selected();
	if (!ti) {
		return;
	}
	String path;
	while (ti) {
		String lp = ti->get_text(0);
		path = "/" + lp + path;
		ti = ti->get_parent();
	}
	NodePath np = path;
	EditorNode::get_singleton()->get_editor_data().set_edited_scene_live_edit_root(np);
	update_live_edit_root();
}
void ScriptEditorDebugger::_live_edit_clear() {