{project} Placeholder not implemented for custom external dotnet editor

[crazyStewie]

Godot version

4.1.1 (Still present on 4df80b0 )

System information

Manjaro Linux, gtx 1060

Issue description

When specifying an external code editor, one has the option to do so by specifying an executable path, and the arguments to be passed to the given executable.

Those arguments can contain certain placeholders (described on https://github.com/godotengine/godot-docs/blob/8a08321d93219228107efac3a8a19594d1ca06ab/tutorials/editor/external_editor.rst?plain=1#L24 ), which get replaced by specific information from the engine when the external editor is launched.

While these arguments seem to work fine when specifying an external text editor via Editor > Editor Settings > Text Editor > External, as is described in the documentation above , only the {file}, {line} and {col} placeholders are implemented for external c# editor, configured under Editor > Editor Settings > Dotnet > Editor (which seems to be undocumented), while the {project} placeholder is left as is. In fact, one can see that, while it is implemented for the external text editor at

godot/editor/plugins/script_editor_plugin.cpp

Lines 2314 to 2318 in 4df80b0

	// do path replacement here, else there will be issues with spaces and quotes
	arg = arg.replacen("{project}", project_path);
	arg = arg.replacen("{file}", script_path);
	args.push_back(arg);

, It's missing on the dotnet external editor implementation at

godot/modules/mono/editor/GodotTools/GodotTools/GodotSharpEditor.cs

Lines 228 to 231 in 4df80b0

	arg = arg.ReplaceN("{file}", file);
	args.Add(arg);

Steps to reproduce

• Make a new godot project with c#
• Go to Editor > Editor Settings > Dotnet > Editor and specify External Editor as custom, and pass in the path to some external editor, like Visual Studio Code
• In Custom Exec Path Args, put in some argument string containing {project} (For vscode, the docs give as an example
  {project} --goto {file}:{line}:{col}
• Open some c# script

Once vscode opens, one will see that, instead of opening the project folder, as one might expect, vscode opens a file with a new file called {project}, since the placeholder was passed directly as an argument, and not replaced with the project path

Minimal reproduction project

N/a (This bug is about an editor setting, which isn't stored as part of a project, so a minimum reproduction project isn't possible)