KIOTA_CONFIG_PREVIEW shouldn't be needed anymore

[maisarissi]

The workspace.json feature was hide behind a env variable KIOTA_CONFIG_PREVIEW

Even for the new version, like 1.19.1 (release) and 1.20 (preview), if one doesn't set KIOTA_CONFIG_PREVIEW, none of the workspace features are available, including all kiota client ... , kiota plugin ... and workspace commands.

Setting the env variable shouldn't be needed anymore and everyone in the newest version should get the new experience by default.

[sebastienlevert]

Partly true. This means that we would be breaking people. We can't do that. This will require a major bump of the library...

[julealgon]

Where can I find more information about this KIOTA_CONFIG_PREVIEW flag?

We are upgrading some of our proxies to latest versions and I saw a mention of this initially here:

• Client update command gains support for specifying lock file path kiota-dotnet#470 (comment)

Then I found this issue.

However, I don't see further details about it anywhere even when searching explicitly on the entire repo.

I'd like to evaluate whether it makes sense for us to be using this flag or not.