### 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
Array msg;
	msg.push_back(p_path);
	msg.push_back(p_line);
	msg.push_back(p_enabled);
	_put_msg("breakpoint", msg, debugging_thread_id != Thread::UNASSIGNED_ID ? debugging_thread_id : Thread::MAIN_ID);
	TreeItem *path_item = breakpoints_tree->search_item_text(p_path);
	if (path_item == nullptr) {
		if (!p_enabled) {
			return;
		}
		path_item = breakpoints_tree->create_item();