fix(natives): Vector3 will generate a tuple type instead of an array …

[AleksanderEvensen]

Goal of this PR

The vector3 type has until now been generated as an array type. In my opinion it should be generated as a tuple type instead.
The reason I think the tuple type is a better option is because it can be used properly with the spread operator in functions that takes in the x, y and z component (ref picture below)

How is this PR achieving the goal

Changing the codegen for dts files to parse the Vector3 type into the tuple type

This PR applies to the following area(s)

Natives

Successfully tested on

Has not been tested due to node-gyp not being able to compile the libclang bindings in native-doc-tooling

Game builds: N/A

Platforms: Windows

Checklist

• Code compiles and has been tested successfully.
• Code explains itself well and/or is documented.
• My commit message explains what the changes do and what they are for.
• No extra compilation warnings are added by these changes. (I won't expect it to generate any errors due to the small change, but I'll leave it uncheck since i haven't tested it)

Fixes issues

N/A

[AvarianKnight]

I think this would be better, though it would generate type errors where there were none before, but also not sure what the opinions on "compatibility breaks" are for types.

I think this change is better for the better as it should always return 3 values

[AleksanderEvensen]

I didn't even think about the compatibility breaking for the types 😅