### 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
next_op = i;
				min_priority = priority;
				is_unary = unary;
				is_ternary = ternary;
			}
		}
		ERR_FAIL_COND_V(next_op == -1, nullptr);
		
		if (is_unary) {
			int expr_pos = next_op;
			while (expression[expr_pos].is_op) {
				expr_pos++;
				if (expr_pos == expression.size()) {
					
					_set_error(RTR("Unexpected end of expression."));
					return nullptr;
				}
			}
			
			for (int i = expr_pos - 1; i >= next_op; i--) {
				OperatorNode *op = alloc_node<OperatorNode>();
				op->op = expression[i].op;
				if ((op->op == OP_INCREMENT || op->op == OP_DECREMENT) && !_validate_assign(expression[i + 1].node, p_function_info)) {
					_set_error(RTR("Invalid use of increment/decrement operator in a constant expression."));
					return nullptr;
				}
				op->arguments.push_back(expression[i + 1].node);
				expression.write[i].is_op = false;