### 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
_put_msg("reload_scripts", Array(), debugging_thread_id != Thread::UNASSIGNED_ID ? debugging_thread_id : Thread::MAIN_ID);
}
bool ScriptEditorDebugger::is_skip_breakpoints() {
	return skip_breakpoints_value;
}
void ScriptEditorDebugger::_error_activated() {
	TreeItem *selected = error_tree->get_selected();
	if (!selected) {
		return;
	}
	TreeItem *ci = selected->get_first_child();
	if (ci) {
		selected->set_collapsed(!selected->is_collapsed());
	}
}
void ScriptEditorDebugger::_error_selected() {
	TreeItem *selected = error_tree->get_selected();
	if (!selected) {
		return;
	}
	Array meta = selected->get_metadata(0);
	if (meta.size() == 0) {
		return;
	}
	emit_signal(SNAME("error_selected"), String(meta[0]), int(meta[1]));
}
void ScriptEditorDebugger::_expand_errors_list() {