Orchestrator Signal and Functions are initialized with incorrect usage flags

[Naros]

Describe the bug

The PropertyInfo struct initializes the usage property as 7 rather than as PROPERTY_USAGE_DEFAULT, which is 6. This seems to be a disconnect between GDExtension's godot-cpp source and the upstream Godot Engine changes made in 2022.

Expected behavior

Signal and Function arguments and return values should be initialized with 6 (PROPERTY_USAGE_DEFAULT).

Actual behavior

Signal and Function arguments and return values should be initialized with 7 (PROPERTY_USAGE_DEFAULT + 1).

How to Reproduce?

Create any Signal or Function and look at its return value or method arguments.

Godot full version

4.2.1-stable

Orchestrator version

2.0.stable

Additional information

Orchestrator can prevent this bug by simply ensuring that the PropertyInfo usage property is initialized using the engine's PROPERTY_USAGE_DEFAULT value rather than relying on the struct's initial value.

We'll likely need to define a clean-up hook for existing Orchestrations to sanitize the OScriptFunction and OScriptSignal definitions. This should not affect standard method data from the serialized engine.

[Naros]

Fixed in godot-cpp as godotengine/godot-cpp#1440

This is being backported for Godot 4.1, 4.2, and fixed in Godot 4.3