I have a custom pipeline step whose signature is (boolean, String, List<String>), and I'm trying to use a chained call.

Due to a bug in CPS, it's trying to pass Integer, GStringImpl, ArrayList, but in the event of the actual Groovy call this should succeed--anything can be run through `asBoolean()`, and GStrings are transparently coerced to regular strings.

I'm not sure how challenging supporting this correctly would be, but these coercions (particularly GStrings) shouldn't trigger the sandbox.