fix(tool): support Flux-returning tool methods

[Alexxigang]

Summary

• add native Flux handling in ToolMethodInvoker instead of treating it as a synchronous object
• stream each emitted Flux item through ToolEmitter so tool chunk callbacks receive incremental updates
• aggregate Flux items into the final tool result while preserving sensible behavior for single-value and multi-value non-string streams
• add regression coverage for invoker-level aggregation/chunk emission and toolkit-level async execution

Why this fix

Issue #938 happens because invokeAsync(...) only special-cases CompletableFuture and Mono. When a tool method returns Flux<?>, the current code falls through the synchronous branch, serializes the Flux object itself, and never subscribes to the stream. That means the parent agent never waits for or consumes the streamed tool output.

This change subscribes to Flux results, forwards intermediate chunks to hooks, and converts the aggregated stream output into the final ToolResultBlock returned to the LLM-facing caller.

Validation

• mvn -pl agentscope-core '-Dtest=AsyncToolTest,ToolMethodInvokerTest' test
• mvn -pl agentscope-core '-Dtest=ToolIntegrationTest' test

AI Assistance

• Drafted with AI assistance and reviewed/validated locally before submission.

[Alexxigang]

Friendly ping when maintainers have time. The change is ready on my side, and I'm happy to make any follow-up adjustments if review feedback comes in. Thanks!

[codecov]

Codecov Report

❌ Patch coverage is 73.46939% with 13 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...ava/io/agentscope/core/tool/ToolMethodInvoker.java	73.46%	4 Missing and 9 partials ⚠️

📢 Thoughts on this report? Let us know!

[LearningGp]

Caution: collectList() collects the entire Flux into memory. Using this on an unbounded or extremely large stream (like a DB cursor) risks triggering an OOM.

[github-actions]

Closing due to inactivity. Feel free to reopen when ready.