Improve login flow, properly init cluster manager

ConnectionManager first tries to login, and only after that starts listening to
configModel changes.

During login flow it updates configModel with authProvider, triggering reloading
of the config state. That's when we load clusterId from the bundle-validate model.

But the clusterId changes never trigger updateClusterManager, since they
happen before ConnectionManager is done with the login and before it started
listening to the changes.

Moving the manual update* calls after we set the auth provider (and awating till
the config model loads all the sub-configs data) fixes the problem.

Author: ilia-db

packages/databricks-vscode/src/configuration/ConnectionManager.ts

@@ -246,14 +246,13 @@ export class ConnectionManager implements Disposable {
                 await this._databricksWorkspace.optionalEnableFilesInReposPopup(
                     this._workspaceClient
                 );
-
-                await this.updateSyncDestinationMapper();
-                await this.updateClusterManager();
                 await this.configModel.set(
                     "authProfile",
                     authProvider.toJSON().profile as string | undefined
                 );
                 await this.configModel.setAuthProvider(authProvider);
+                await this.updateSyncDestinationMapper();
+                await this.updateClusterManager();
                 await this._metadataService.setApiClient(this.apiClient);
                 this.updateState("CONNECTED");
             });