feat(Handler/enablement): Add enablement state query handler for extension management

Implement handler for retrieving extension enablement state in Mountain backend. This initial implementation returns a default 'enabled' state (EnabledGlobally=1) to support MVP requirements where extensions sent to Cocoon are considered active.

- Integrates with Mountain's RPC command handling through Track dispatcher
- Provides temporary implementation matching Path A strategy of minimal shim layer changes
- Enables Cocoon extension host to perform basic enablement checks required by VS Code extension API surface
- Prepares foundation for future integration with persistent AppState storage once enablement service is implemented

Author: NikolaRHristov

Source/handlers/enablement.rs

@@ -0,0 +1,13 @@
+use serde_json::{Value, json};
+use tauri::{AppHandle, Runtime};
+// Assume Mountain has access to the real IWorkbenchExtensionEnablementService state
+
+pub async fn handle_get_enablement_state<R: Runtime>(_app: AppHandle<R>, params: Value) -> Result<Value, String> {
+    let extension_id = params.get("extensionId").and_then(|v| v.as_str()); // Extract ID
+    println!("[Enablement Handler] GetState request for {:?}", extension_id);
+    // TODO: Query the actual enablement service state in Mountain
+    // For MVP, assume enabled if it was sent to Cocoon in the first place
+    let enabled_state = 1; // Example: EnabledGlobally
+    Ok(json!(enabled_state))
+}
+// TODO: Add handlers for setEnablement etc. if needed by shim