### 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
}
							}
						}
					} else {
						for (int i = 0; i < p_render_modes.size(); i++) {
							const ModeInfo &info = p_render_modes[i];
							const String name = String(info.name);
							if (smode.begins_with(name)) {
								if (!info.options.is_empty()) {
									if (info.options.has(smode.substr(name.length() + 1))) {
										found = true;
										if (defined_modes.has(name)) {
											_set_error(vformat(RTR("Redefinition of render mode: '%s'. The '%s' mode has already been set to '%s'."), smode, name, defined_modes[name]));
											return ERR_PARSE_ERROR;
										}
										defined_modes.insert(name, smode);
										break;
									}
								} else {
									found = true;
									break;
								}
							}
						}
					}
					if (!found) {
						_set_error(vformat(RTR("Invalid render mode: '%s'."), smode));
						return ERR_PARSE_ERROR;
					}
					shader->render_modes.push_back(mode);