Always use new token issuing flow

What does this MR do and why?

Always use new token issuing flow.

This is a refactor. We migrated a set of unit primitives to the new Token Issuing interface for Cloud Connector.
Now we want to use this flow by default.

This MR also cleans up corresponding feature flags as they were rolled out:

How to set up and validate locally

This is no-op change.
But for safety, we can ensure Code Completion works as expected (we need to run as SaaS).

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #561289 (closed)

Edited by Aleksei Lipniagov

Merge request reports

Loading