fix(vscode): await schema registry initialization before validating documents

- Change ValidationService.register() to async and await schema initialization
- Prevents race condition where documents might be validated before schemas are loaded
- Particularly important if schema loading becomes remote in the future

Addresses PR feedback from @willosborne regarding void promise handling

Author: rocketstack-matt

calm-plugins/vscode/src/calm-extension-controller.ts

@@ -85,9 +85,9 @@ export class CalmExtensionController {
 
     new CommandRegistrar(context, store).registerAll()
 
-    // Initialize validation service
+    // Initialize validation service (await to ensure schemas are loaded before validating documents)
     const validationService = new ValidationService(log, configService)
-    validationService.register(context)
+    await validationService.register(context)
 
     const storeReactionMediator = new StoreReactionMediator(
       store,

calm-plugins/vscode/src/features/validation/validation-service.ts

@@ -41,11 +41,12 @@ export class ValidationService implements vscode.Disposable {
 
     /**
      * Register document listeners to trigger validation on save.
+     * Async to ensure schema registry is fully initialized before validating documents.
      */
-    register(context: vscode.ExtensionContext): void {
+    async register(context: vscode.ExtensionContext): Promise<void> {
         // Initialize the schema registry with bundled schemas
         this.schemaRegistry = new CalmSchemaRegistry(context.extensionUri, this.logger, this.config)
-        void this.schemaRegistry.initialize()
+        await this.schemaRegistry.initialize()
 
         // Listen for configuration changes to reset schema registry
         this.disposables.push(