feat(plugins): load activation scope from plugin manifest

Plugins can now declare activationScope ("app" | "project") in their
manifest; loader/runtime honor it to defer activation of project-scoped
plugins until a project is focused instead of activating everything at
app bootstrap. Bumps sdk/IdeaSDK to the commit that adds the field.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

crates/app-tauri/tests/dto_plugins.rs

@@ -49,6 +49,7 @@ fn runtime_catalog_dto_carries_bundle_hash_and_contributions() {
             icon_url: None,
             content_hash: "abc".to_owned(),
             capabilities: vec![PluginCapability::Ui, PluginCapability::Tooling],
+            activation_scope: domain::PluginActivationScope::Project,
             contributes: PluginContributionSet::default(),
         }],
     };
@@ -63,6 +64,7 @@ fn runtime_catalog_dto_carries_bundle_hash_and_contributions() {
         value["plugins"][0]["capabilities"],
         serde_json::json!(["ui", "tooling"])
     );
+    assert_eq!(value["plugins"][0]["activationScope"], "project");
     assert!(value["plugins"][0]["contributes"]["menus"]
         .as_array()
         .unwrap()