### Godot version

4.0.3, 4.1-dev1, 4.1-dev2

### System information

Windows 11, ASUS Zephyrus G14 2022, Ryzen 9, Radeon 6700S

### Issue description

If you create a custom class script and extend it in a custom sub class script using GDScript, override `_init()` in the sub class but not in the parent class, and then call `super()` in the sub class, it will run fine in the editor or if exported with the debug template. However, if you export a release build, the `super()` call will induce a script error.

I think the bug is that the debugger should throw an error in this case. Trying the same with methods like `_ready` for classes extending nodes or even `_to_string` for a RefCounted class and running in the editor will cause a script error to be caught by the debugger.

In editor:
![debug](https://github.com/godotengine/godot/assets/125445387/f6da77c5-c9d3-4bb9-a4b0-80d2f9218033)

Release build:
![release_error](https://github.com/godotengine/godot/assets/125445387/73a9d098-7c3b-45e4-8761-e3f40ffd3bc9)


### Steps to reproduce

Create two classes
ClassTwo extends ClassOne
ClassTwo overrides virtual method _init() (**ClassOne does not**)
ClassTwo calls super() in _init()
No error in debug/editor
Error in release

### Minimal reproduction project

N/A
#ifndef GDSCRIPT_ANALYZER_H
#define GDSCRIPT_ANALYZER_H
#include "gdscript_cache.h"
#include "gdscript_parser.h"
#include "core/object/object.h"
#include "core/object/ref_counted.h"
#include "core/templates/hash_set.h"
class GDScriptAnalyzer {
	GDScriptParser *parser = nullptr;
	HashMap<String, Ref<GDScriptParserRef>> depended_parsers;
	const GDScriptParser::EnumNode *current_enum = nullptr;
	List<GDScriptParser::LambdaNode *> lambda_stack;
	bool static_context = false;
	
	static _FORCE_INLINE_ bool has_member_name_conflict_in_script_class(const StringName &p_name, const GDScriptParser::ClassNode *p_current_class_node, const GDScriptParser::Node *p_member);
	static _FORCE_INLINE_ bool has_member_name_conflict_in_native_type(const StringName &p_name, const StringName &p_native_type_string);