### 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
if (is_uniform) {
						_set_error(vformat(RTR("The '%s' data type is not supported for uniforms."), "struct"));
						return ERR_PARSE_ERROR;
					} else {
						_set_error(vformat(RTR("The '%s' data type is not allowed here."), "struct"));
						return ERR_PARSE_ERROR;
					}
				}
				if (!is_token_datatype(tk.type)) {
					_set_error(RTR("Expected data type."));
					return ERR_PARSE_ERROR;
				}
				type = get_token_datatype(tk.type);
				if (precision != PRECISION_DEFAULT && _validate_precision(type, precision) != OK) {
					return ERR_PARSE_ERROR;
				}
				if (type == TYPE_VOID) {
					_set_error(vformat(RTR("The '%s' data type is not allowed here."), "void"));
					return ERR_PARSE_ERROR;
				}
				if (!is_uniform && interpolation != INTERPOLATION_DEFAULT && type < TYPE_INT) {
					_set_error(vformat(RTR("Interpolation modifier '%s' cannot be used with boolean types."), get_interpolation_name(interpolation)));
					return ERR_PARSE_ERROR;
				}
				if (!is_uniform && type > TYPE_MAT4) {
					_set_error(RTR("Invalid data type for varying."));
					return ERR_PARSE_ERROR;
				}
#ifdef DEBUG_ENABLED
				keyword_completion_context = CF_UNSPECIFIED;