implement union type support for streaming actions

[ThyTran1402]

Summary

Extends the @streaming_action.pydantic() decorator to accept union types like Model1 | Model2 or Union[Model1, Model2]) for the stream_type parameter. Previously, only single BaseModel types or dict were accepted, limiting flexibility for streaming actions that yield multiple result types.

Changes

• burr/core/action.py
• burr/integrations/pydantic.py
• tests/integrations/test_streaming_union_types.py

How I tested this

Unit Tests: Created comprehensive test suite with 10 tests that all pass

Notes

Resolved: #607

Checklist

• PR has an informative and human-readable title (this will be pulled into the release notes)
• Changes are limited to a single goal (no scope creep)
• Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future TODOs are captured in comments
• Project documentation has been updated if adding/changing functionality.

[Ghraven]

Thanks for picking this up and for writing out the investigation so clearly.

One small thought from my earlier pass on this issue: adding object to the union does make the type checker accept union values, but it also effectively widens stream_type to almost any value. That may still be the pragmatic choice here, but maintainers may prefer either a more explicit alias/comment around why the parameter is intentionally broad, or a small runtime/type-helper path that recognizes union forms while keeping the public intent narrow.

The focused tests for both yping.Union[...] and ModelA | ModelB look useful. Thanks again for moving this forward.