feat: sidebar plugin config UI

src/slic3r/plugin/PluginResolver.hpp

@@ -4,6 +4,7 @@
 #include <libslic3r/Config.hpp>   // PluginCapabilityRef, parse_capability_ref
 #include <libslic3r/Preset.hpp>   // Preset::Type
 #include <libslic3r/PresetBundle.hpp>
+#include <slic3r/plugin/PluginLoader.hpp> // PluginCapabilityIdentifier
 #include <slic3r/plugin/PythonPluginInterface.hpp> // PluginCapabilityType
 #include <cstddef>
 #include <functional>
@@ -81,6 +82,21 @@ void open_missing_plugins_on_cloud(const std::vector<std::string>& local_refs);
 std::string create_full_ref(const PluginCapabilityRef& ref);
 std::string resolve_recovery_url(const PluginCapabilityRef& ref);
 
+// The capabilities `preset`'s "plugins" manifest declares AND that one of its plugin-backed options
+// (ConfigOptionDef::is_plugin_backed) currently references. A manifest entry nobody points at is not
+// in use. Pure preset logic — the plugin catalog and loader are not consulted. Empty for untracked
+// preset types.
+std::vector<PluginCapabilityRef> referenced_capabilities(Preset::Type type, const Preset& preset);
+std::vector<PluginCapabilityIdentifier> capabilities_in_use(Preset::Type type, const Preset& preset);
+
+// The capabilities the active preset(s) of `type` reference (see referenced_capabilities) and that
+// are loaded right now: the set that can actually be configured. Missing and broken refs are absent,
+// having no instance to ask for a config UI or defaults. A loaded-but-disabled capability IS listed —
+// it still has stored config worth editing, and disabling it is not a reason to hide that.
+// TYPE_FILAMENT unions every selected filament preset; a capability used by two extruders is listed
+// once. Deduped on the full identity, so two plugins exposing a same-named capability stay distinct.
+std::vector<PluginCapabilityIdentifier> capabilities_in_use(const PresetBundle& preset_bundle, Preset::Type type);
+
 bool check_capability_in_use(const std::string& capability_refs);
 
 } // namespace Slic3r