Implement better function argument ordering parsing

[APickledWalrus]

Problem

Currently, the enhanced function argument parsing with named arguments is too restrictive when optional parameters exist. For example, the following function call errors for a somewhat unclear reason: set {_loc} to location(x: 1, y: 1, z: 1, yaw: 1, pitch: 1) (Mixing named and unnamed arguments is not allowed unless the order of the arguments matches the order of the parameters.). This error is because the world parameter must occur before the yaw parameter. However, given that it is optional. one would expect for this function call to work without issue.

Solution

I have reworked the function argument parsing so that the user provided arguments are instead reworked into the order defined by the function signature. First, all named parameters are inserted into their respective positions. Then, the remaining unnamed arguments are inserted into the remaining positions. An unnamed parameter is only valid in its position if the named parameter it represents occurs before all named parameters that come after in the user's provided arguments.

For example, the following calls are now valid:
location(1, 2, 3, pitch: 10, yaw: 5) where 1, 2, and 3 represent x, y, and z respectively
location(x: 1, y: 2, z: 3, yaw: 4, 5) where 5 represents pitch
location(x: 1, 2, z: 3) where 2representsy`.

Further, I fixed a mistake where failures to parse arguments as expressions would result in the default value being used. Instead, an error about the input being invalid for that parameter is now parsed.

Testing Completed

I have added a few additional tests to StructFunction.sk

Supporting Information

n/a

---

Completes: none
Related: none
AI assistance: none

[Efnilite]

some extra comments would be appreciated 🙏

[Efnilite]

looks good, although the getExactReferences method is now quite long and complicated. future improvements could split it up tho. nice 🔥