Fix unintentionally calling to_a on the target

[dorner]

The fix in #448 had some unintented consequences. We have a custom to_a method on one of our ActiveRecord objects which returns a set of different ActiveRecord objects. (Yes, I'm well aware this violates the Law of Least Surprise, but it was done ages ago and is now so baked into our code that extracting it would be a major undertaking.)

The current code "splats" the target of turbo_stream_action_tag to pass to the dom_id method. The problem is that it's assuming that the object is "array-like" - which the Array() method does not ensure. It uses to_ary or to_a to return an array, but doesn't indicate that the object itself is in fact an array.

This PR fixes this by using Array.wrap, ensuring we actually have an array, and splatting the array into the method rather than the original target (which would call to_a again).

I wasn't able to find a contribution guideline page, so please let me know if anything else needs to be done here (do I need to create an issue?)

[seanpdoyle]

Thank you! Great catch.

[dorner]

@seanpdoyle thanks for the approval - any idea when it can be merged?

[dorner]

@seanpdoyle bumping this :) Still not fixed in latest turbo-rails.

[seanpdoyle]

@afcapel could you review this?

[brunoprietog]

Thanks @dorner!