Connect framework incorrectly instantiates TaskStates for REST extensions

The TaskState class's constructor takes in parameters for the task's ID number, state, worker, and (optionally-null) error stack trace, in that order. However, the Connect framework's ConnectClusterStateImpl class instantiates TaskState objects with a different ordering of arguments: ID number, worker, state, trace.

It's possible that this (erroneous) behavior has already been identified and worked around by developers of REST extensions, so it's questionable whether a patch PR here is warranted.