Expose ImportWorkflow Endpoint

[ofimbres]

Why are these changes needed?

As of Sep 29th, there is an existing endpoint in autogen studio backend for exporting an entire workflow (including agents, models and skills), but no import workflow. This PR exposes a new endpoint for importing a workflow based on the output generated by export workflow and persist it into the database.

Checks

• I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
• I've added tests (if relevant) corresponding to the changes introduced in this PR.
• I've made sure all auto checks have passed.

[victordibia]

Hi,

@ofimbres , Thanks for this PR.
Adding new datamodels tends to break existing db schema.
There is some work to be done to enable automatic database upgrade e..g, detect schema differences and update the database. (not specific to this PR, but useful overall for ags)
Any chance you have explored this or have some thoughts?

[ofimbres]

Hi,

@ofimbres , Thanks for this PR. Adding new datamodels tends to break existing db schema. There is some work to be done to enable automatic database upgrade e..g, detect schema differences and update the database. (not specific to this PR, but useful overall for ags) Any chance you have explored this or have some thoughts?

@victordibia This schema uses the same schema used for export. Export uses a new schema that is not defined by pydantic, as a dict. Now that there is a new version, I will look into the new architecture changes and rebase them