[Feature Request] Unify streaming-response handling across workforce/task flows

[coolbeevip]

Required prerequisites

• I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
• Consider asking first in a Discussion.

Motivation

I found that some workforce .step / .astep paths (e.g. task analysis, assignment, worker creation) assume non-streaming responses and do not check the returned response type.

When the default model is configured to stream, these steps may receive streaming responses (or generators), which leads to parsing errors or dropped content.

Solution

Add a shared streaming-response helper under camel/utils to detect and consume streaming responses (sync & async)

Alternatives

No response

Additional context

No response