feat(flow): add podcast flow

[bridgeqiqi]

Description

Refer to #54

Checklist

Please feel free to remove inapplicable items for your PR.

• The PR title starts with $CATEGORY(xx): xxx (such as feat(tool): xxx, fix(source): xxx, docs(README): xxx)
• Related issue is referred in this PR
• The markdown and latex are rendered correctly.
• The code in PR is well-documented.
• The PR is complete and small, read the Google eng practice (CL equals to PR) to understand more about small PR.

[wanghaoxue0]

looks good from my side

[WinstonLiyt]

I tried to fix some bugs in PR 53.

[keli-wen]

Great job on this pull request! This is a really well-structured and useful addition.

I have a couple of suggestions for discussion:

1. Built-in vs. Example Flow: I'd like to propose that we discuss whether the podcast_flow should be a core, built-in flow or if it would serve a better purpose as a detailed example. My perspective is that it functions as an excellent demonstration of how to customize a personal flow to achieve a specific goal. Positioning it as a showcase in the examples/ directory could be a great way to guide users in creating their own solutions.

2. Dedicated PodcastFlowConfig: To improve flexibility, what are your thoughts on defining a specific PodcastFlowConfig? This would allow us to add more granular controls, such as managing the number of speakers in the podcast (e.g., defaulting to two). This would make the flow more adaptable for different podcast formats.

These are just a couple of points for discussion. Overall, this is excellent work and very close to being ready. Great job

[keli-wen]

Since I sync the latest branch, pull it before dev it.

[bridgeqiqi]

Great job on this pull request! This is a really well-structured and useful addition.

I have a couple of suggestions for discussion:

1. Built-in vs. Example Flow: I'd like to propose that we discuss whether the podcast_flow should be a core, built-in flow or if it would serve a better purpose as a detailed example. My perspective is that it functions as an excellent demonstration of how to customize a personal flow to achieve a specific goal. Positioning it as a showcase in the examples/ directory could be a great way to guide users in creating their own solutions.
2. Dedicated PodcastFlowConfig: To improve flexibility, what are your thoughts on defining a specific PodcastFlowConfig? This would allow us to add more granular controls, such as managing the number of speakers in the podcast (e.g., defaulting to two). This would make the flow more adaptable for different podcast formats.

These are just a couple of points for discussion. Overall, this is excellent work and very close to being ready. Great job

@keli-wen Good points of view!
For No. 1, it depends on the scope and mission of the quant-mind, in my opinion. The role of podcast_flow might be the same as that of summary_flow, etc. If quant-mind plays the role of providing more efficient engine or infra, the customized flow will serve as the application layer to leverage the flow infra.
For No. 2, Good points. We can definitely add more specific attributes in the flow configuration. Agreed to you, it would be better we could provide a PodcastFlowConfig here to make it more adaptable for different users to customize.

[keli-wen]

LGTM, just to confirm, can the podcast flow currently run successfully? (Based on OpenAI API)

[bridgeqiqi]

LGTM, just to confirm, can the podcast flow currently run successfully? (Based on OpenAI API)

Yes. I tested pipeline.py with OpenAI API. It runs successfully.