ISS-33: Fixed and expanded array functions

[Alphish]

As it turned out, using plain script_execute_ext(...) with large arrays caused some stack overflow error. More details in issue #33

Also, I added extra offset and length parameters, working similarly to same parameters in native array functions (like array_filter or array_map). Generally:

• a positive offset is counted forward from the start of the array; a negative offset is counted backwards from the end of the array (with -1 being the last element index, or array length minus one); if absolute value of negative offset exceeds array length, offset of 0 is used
• a positive length counts items forward from the offset (included); a negative length counts items backwards from the offset (also included); if the length exceeds available items (e.g. from 7th offset onwards there are only 5 items, and length of 10 was given), then only the available items are processed

[Mercerenies]

Idle thought, but given that we ran into stack overflow issues, it's worth considering. I wonder if the stack size is smaller on mobile. 10,000 is likely to be fine on desktop platforms, but it's possible that this will still overflow the stack on a smaller device. I haven't tested it, but food for thought.

[Alphish]

I haven't really been involved with mobile development in GM, so I guess I'll use the "we'll think about it once someone finds the problem" approach. If need be, we might implement some script_execute_max_args() function that chooses the number depending on the platform.

[Mercerenies]

Fair enough. 👍

[Mercerenies]

Looks good :)