### 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
for (const KeyValue<ShaderWarning::Code, HashMap<StringName, HashMap<StringName, Usage>> *> &E : warnings_check_map2) {
		for (const KeyValue<StringName, HashMap<StringName, Usage>> &T : *E.value) {
			for (const KeyValue<StringName, Usage> &U : T.value) {
				if (!U.value.used) {
					_add_warning(E.key, U.value.decl_line, U.key);
				}
			}
		}
	}
	for (const KeyValue<ShaderWarning::Code, HashMap<StringName, Usage> *> &E : warnings_check_map) {
		for (const KeyValue<StringName, Usage> &U : (*E.value)) {
			if (!U.value.used) {
				_add_warning(E.key, U.value.decl_line, U.key);
			}
		}
	}
}
List<ShaderWarning>::Element *ShaderLanguage::get_warnings_ptr() {
	return warnings.front();
}
void ShaderLanguage::enable_warning_checking(bool p_enabled) {
	check_warnings = p_enabled;
}
bool ShaderLanguage::is_warning_checking_enabled() const {