Provide an optional switch when plugin generation is happening in Kiota to avoid creating .kiota folder. See related issues #6465, #6466

Challenge

.kiota folder is a vital piece for Kiota VS Code extension to work properly while providing all functionalities Kiota has to offer, like listing all client/plugin and enabling regeneration.
However, Kiota is now more than a standalone CLI and VS Code extension, Kiota will power both Teams Toolkit and TypeSpec experiences when one wants to generate plugins and .kiota folder shouldn't be requirement in those experiences.

Proposal

Add a new switch --no-workspace.

--no-workspace should be provided for the "new commands" available for those using the workspace experience. (https://github.com/microsoft/kiota/blob/main/specs/scenarios/kiota-workspace.md and plugins https://github.com/microsoft/kiota/blob/main/specs/scenarios/plugins.md)

Evaluate

• Map that to a new generation setting, which can be also exposed on the JSON RPC and TS API surface.
• That can then drive workspace steps in the main generation for both the plugins and the clients
• Log files will be written using output path