### Godot version

v4.0.beta13.official [caacade56]

### System information

Linux Ubuntu 20.04 with Unity desktop

### Issue description

When calling an undefined function in the shader editor with argument(s), such as `undefined_function(1)`, the error reads:

> Too many arguments for "undefined_function()" call. Expected at most 0 but received 1.

instead of the expected:

> No matching function found for: 'undefined_function'.

This is possibly a regression introduced in https://github.com/godotengine/godot/issues/18225, since the latter was focused on the arguments part.

To avoid such regression in the future, consider adding a unit test with this case (and, in fact, unit tests for the other signature errors too if there are not already).

### Steps to reproduce

1. Create a shader resource and open the shader editor
2. Enter `undefined_function(1);` in the fragment() definition

### Minimal reproduction project

N/A
int texture_binding = 0;
	int uniforms = 0;
	int instance_index = 0;
#ifdef DEBUG_ENABLED
	uint64_t uniform_buffer_size = 0;
	uint64_t max_uniform_buffer_size = 0;
	int uniform_buffer_exceeded_line = -1;
	bool check_device_limit_warnings = false;
	{
		RenderingDevice *device = RenderingDevice::get_singleton();
		if (device != nullptr) {
			check_device_limit_warnings = check_warnings && HAS_WARNING(ShaderWarning::DEVICE_LIMIT_EXCEEDED_FLAG);
			max_uniform_buffer_size = device->limit_get(RenderingDevice::LIMIT_MAX_UNIFORM_BUFFER_SIZE);
		}
	}
#endif 
	ShaderNode::Uniform::Scope uniform_scope = ShaderNode::Uniform::SCOPE_LOCAL;
	stages = &p_functions;
	const FunctionInfo &constants = p_functions.has("constants") ? p_functions["constants"] : FunctionInfo();
	HashMap<String, String> defined_modes;
	while (tk.type != TK_EOF) {
		switch (tk.type) {
			case TK_RENDER_MODE: {
#ifdef DEBUG_ENABLED
				keyword_completion_context = CF_UNSPECIFIED;
#endif 
				while (true) {
					StringName mode;
					_get_completable_identifier(nullptr, COMPLETION_RENDER_MODE, mode);
					if (mode == StringName()) {