Add switch to avoid creation of .kiota folder for legacy lock experience

Provide an optional switch when generation is happening in Kiota to avoid creating `.kiota` folder. See related issue #6452

### Overview
Add a new switch --no-lock to avoid creating the .kiota folder.

--no-lock should be provided for the "old commands" available for those using the lock experience.

### 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
- Where to place the log files? It's probably ok to leave a .kiota with a log file in there for the time being.
- Add a hidden environment variable KIOTA_DISABLE_LOG_FILES in case one doesn't want to get the generated logs?

Start with related issue #6452, then trace the old commands and generation settings described here. Determine how a --no-lock switch should reach the JSON RPC and TypeScript API surfaces and drive workspace steps for plugins and clients; done means the switch avoids creating .kiota for legacy commands while the log-file behavior is decided.

Written by the indexing model from the issue text.