Fix argument validation in WorkflowHandle for issue #1327

[Vignesh18280]

#1327

What was changed This PR fixes the argument validation for WorkflowHandle. It ensures that the args parameter is always validated as an array and throws an appropriate error if it is not.

Why? To address issue #1327, improving error handling and clarity for users by ensuring the args passed to workflows are always arrays.

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[mjameswh]

Thanks for your contribution.

Can you please clarify the use case that would result in seeing this error message?

The TypeScript signature for that function no longer allows passing a non-array to args, and we generally do not add type checking for pure JS use cases.

[Vignesh18280]

@mjameswh Thanks for the response. It's true that TypeScript enforces array inputs for args. However, since the issue remained open, I assumed that Temporal wanted to implement additional error handling for potential edge cases, particularly in JavaScript environments where type safety isn't as strict. I aimed to add that validation to ensure better runtime safety. Let me know if this approach aligns with the goal!

[mjameswh]

I see. Then thanks again, but I'd prefer not changing this.