DynamicFormOrchestrator

[dennisfeng200]

The DynamicFormOrchestrator should be now in a working state for profile gen, which uses the "conversation_without_data" method. The "conversation_with_data" is in a working state, but I added TODO comments on possible improvements for the future if we want to build it out further.

Changes :

• switched from requirements.txt file to using poetry files (pyproject.toml, poetry.lock). Note that we can run a CLI command to generate a requirements.txt file from the poetry.lock, if needed.
• created DynamicFormOrchestrator and some pytests for it
• modified Orchestrator to dump all env params in a 'env_params' attribute, which encapsulates the params better for DynamicFormOrchestrator
• the Topic/ProfileMatchingUI branch was merged into this branch at an earlier point, in order to get some of the working frontend for testing here. Topic/ProfilingMatchingUI probably now has a lot more updates which I believe should overwrite the older commits here.
• ...

Some features to point out that are NOT implemented, due to time constraint and priority:

• for conversation_with_data: attaching a file is not supported, and cosmosDB data source is not supported (azure AI search is though!). These features probably won't be needed for profile gen chat.
• when using conversation_without_data (the primary use case for profile gen), it is only programmatically guaranteed that 'dynamic_form_data' (in the HTTP response) exists as an object (of any type). There is NO guarantee that it matches the exact structure you defined in the prompt; that's a prompt engineering problem.

[tendau]

We cannot bring the GC specific UI into main. This either needs to live with the GC branch (deployment) or be pulled out