dify - 💡(How to fix) Fix Cache plugin model provider discovery across runs with tenant-scoped invalidation [1 pull requests]

Summary

Plugin-backed model provider discovery currently relies on repeated daemon reads in runtime paths. This can add avoidable latency across workflow/app runs and makes cache ownership harder to reason about when plugin lifecycle operations mutate installed provider metadata.

Proposal

Add a tenant-scoped TTL cache for plugin model provider discovery and make plugin lifecycle operations invalidate that cache when a tenant installs, uninstalls, or upgrades plugins.

Keep the cache owner inside the core plugin layer so provider reads and plugin lifecycle mutations share one implementation boundary. PluginModelRuntime should receive the plugin service dependency during construction and delegate provider discovery to it.

Expected impact

• Reuse plugin model provider metadata across runs while preserving tenant isolation.
• Avoid request-scoped provider caches that can diverge from plugin lifecycle changes.
• Centralize plugin provider metadata cache read/write/invalidation behavior in the core plugin service.