### 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 
			}
#ifdef DEBUG_ENABLED
			if (is_const && _lookup_next(next)) {
				if (is_token_precision(next.type)) {
					keyword_completion_context = CF_UNSPECIFIED;
				}
				if (is_token_datatype(next.type)) {
					keyword_completion_context ^= CF_DATATYPE;
				}
			}
#endif 
			if (precision != PRECISION_DEFAULT) {
				if (!is_token_nonvoid_datatype(tk.type)) {
					_set_error(RTR("Expected variable type after precision modifier."));
					return ERR_PARSE_ERROR;
				}
			}
			if (!is_struct) {
				if (!is_token_variable_datatype(tk.type)) {
					_set_error(RTR("Invalid variable type (samplers are not allowed)."));
					return ERR_PARSE_ERROR;
				}
			}
			DataType type = is_struct ? TYPE_STRUCT : get_token_datatype(tk.type);
			if (precision != PRECISION_DEFAULT && _validate_precision(type, precision) != OK) {
				return ERR_PARSE_ERROR;
			}
#ifdef DEBUG_ENABLED