TTK and Kiota integrated flow should support regeneration of plugins

[sebastienlevert]

As part of the command-base integration between Kiota and TTK, .kiota folder should be supported.
.kiota folder includes the following:

workspace.json file, which is Kiota's input files used to generate clients and plugins. So, supporting this in the integration is vital to help one maintaining their clients/plugins.
apimanifest.json file, which represents a snapshot and a concatenated surface of all APIs used across plugins and clients. Both files, apimanifest.json and workspace.json will be used to generate the code files. A new hash composed of the Kiota version, the OpenAPI document location and the properties of the manifest will be generated and would trigger an update to the API Manifest in case there is any change.
documents folder, which contains a copy of all OpenAPI descriptions used to generate clients/plugins
As previous discussed with TTK team, supporting users in editing existing plugins, is one of their current goals and Kiota can provide that.
Once .kiota folder is supported in fx-extension.createprojectfromkiota command, Kiota will need to update its code to pass the right values.

Related to: OfficeDev/teams-toolkit#12489

[maisarissi]

I can't edit the initial description so I'm going to add the description as a comment:

As part of the command-base integration between Kiota and TTK, .kiota folder should be supported.
.kiota folder includes the following:

• workspace.json file, which is Kiota's input files used to generate clients and plugins. So, supporting this in the integration is vital to help one maintaining their clients/plugins.
• apimanifest.json file, which represents a snapshot and a concatenated surface of all APIs used across plugins and clients. Both files, apimanifest.json and workspace.json will be used to generate the code files. A new hash composed of the Kiota version, the OpenAPI document location and the properties of the manifest will be generated and would trigger an update to the API Manifest in case there is any change.
• documents folder, which contains a copy of all OpenAPI descriptions used to generate clients/plugins

As previous discussed with TTK team, supporting users in editing existing plugins, is one of their current goals and Kiota can provide that.
Once .kiota folder is supported in fx-extension.createprojectfromkiota command, Kiota will need to update its code to pass the right values.

Related to: OfficeDev/teams-toolkit#12489

[maisarissi]

Updates from our planning today:

As part of the .kiota folder support we need to call TTK for regenerating adaptive cards for Ignite 24 timeframe.

If we do have time/people to work on other priorities for Ignite, we should focus on supporting adaptive cards generation in Kiota

We need to support adaptive cards generation so we can cover the regeneration flow properly and TTK can drop their adaptive cards support.