Duplicating agent: Compatibility issues between Flow Registry YAML capability and current AI Catalog schema limitations

Duplicating the agent will be an interesting task, as it involves copying from Foundational agent type to a custom AI Catalog agent type.

• Flow Registry YAML and current AI Catalog agent schema are not the same.
• Flow Registry YAML can have more capabilities than AI Catalog agent schema, so are not equivalent.

Initial thoughts of our options:

1. Could disable copying for first iteration?
2. Could copy subset of functionality that AI Catalog agent v1 schema allows (and document restriction).
3. Release AI Catalog agent schema v2 which will have 1:1 compatibility with v1 Flow Registry - however, we would need to allowlist the YAML that we copy as we can still have differences, where something is added to Flow Registry v1 before AI Catalog agent schema v2.

Maybe 1 or 2 for the initial iteration, and 3 as a post-GA work.