### 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
#endif 
					completion_type = COMPLETION_NONE;
					current_uniform_hint = ShaderNode::Uniform::HINT_NONE;
					current_uniform_filter = FILTER_DEFAULT;
					current_uniform_repeat = REPEAT_DEFAULT;
					current_uniform_instance_index_defined = false;
				} else { 
					ShaderNode::Varying varying;
					varying.type = type;
					varying.precision = precision;
					varying.interpolation = interpolation;
					varying.tkpos = prev_pos;
					varying.array_size = array_size;
					tk = _get_token();
					if (tk.type != TK_SEMICOLON && tk.type != TK_BRACKET_OPEN) {
						if (array_size == 0) {
							_set_expected_error(";", "[");
						} else {
							_set_expected_error(";");
						}
						return ERR_PARSE_ERROR;
					}
					if (tk.type == TK_BRACKET_OPEN) {
						Error error = _parse_array_size(nullptr, constants, true, nullptr, &varying.array_size, nullptr);
						if (error != OK) {
							return error;
						}
						tk = _get_token();
					}
					shader->varyings[name] = varying;