fix: 释放 Windows 插件目录占用

[yg2224]

Summary

• 删除开发项目时，先停止仍在运行的开发态插件，避免 Windows 下插件目录持续被占用
• 从已安装插件列表中移除对应的开发态记录，避免删除后仍残留旧路径引用
• 删除普通插件目录前也先尝试释放运行中的插件实例

[gemini-code-assist]

Code Review

This pull request introduces logic to ensure that plugins are properly terminated before they are removed from the registry or the installed list. The review feedback suggests simplifying the path identification and list filtering logic in the development projects API for better readability. Additionally, it points out that a try-catch block in the plugins API is redundant because the underlying kill method already handles internal errors.

[gemini-code-assist]

The logic for identifying the plugin path and removing it from the installed list can be simplified. Using the object reference returned by find for the filter operation is more efficient and readable. Additionally, the fallback logic for killPath can be expressed more concisely.

Suggested change

	const registryEntry = registry.projects[projectName]
	const devEffectiveName = toDevPluginName(projectName)
	const plugins = this.deps.readInstalledPlugins()
	const installedDevPlugin = plugins.find(
	(p) => p?.isDevelopment && p?.name === devEffectiveName
	)
	const runningPluginPath =
	typeof installedDevPlugin?.path === 'string' && installedDevPlugin.path
	? installedDevPlugin.path
	: registryEntry.projectPath
	if (typeof runningPluginPath === 'string' && runningPluginPath) {
	this.deps.pluginManager?.killPlugin(runningPluginPath)
	}
	if (installedDevPlugin?.isDevelopment) {
	this.deps.writeInstalledPlugins(
	plugins.filter((p) => !(p?.isDevelopment && p?.name === devEffectiveName))
	)
	}
	const registryEntry = registry.projects[projectName]
	const devEffectiveName = toDevPluginName(projectName)
	const plugins = this.deps.readInstalledPlugins()
	const installedDevPlugin = plugins.find(
	(p) => p?.isDevelopment && p?.name === devEffectiveName
	)
	const killPath = installedDevPlugin?.path || registryEntry.projectPath
	if (killPath) {
	this.deps.pluginManager?.killPlugin(killPath)
	}
	if (installedDevPlugin) {
	this.deps.writeInstalledPlugins(plugins.filter((p) => p !== installedDevPlugin))
	}

[yg2224]

已收敛 killPath 分支，并补了针对性测试。这里保留按 isDevelopment + name 清理已安装列表，而不是只按对象引用删 1 条，因为删除开发项目时需要把同名开发态残留项一并清掉，避免脏数据下继续留下旧路径记录。

[gemini-code-assist]

The try-catch block here is redundant because pluginManager.killPlugin already implements its own internal try-catch and does not throw. You can simplify this to a single optional call.

      this.pluginManager?.killPlugin(pluginPath)

[yg2224]

外层 ry/catch 已移除，删除前现在直接调用 his.pluginManager?.killPlugin(pluginPath)。另外补了删除路径上的回归测试。

[yg2224]

已去掉 deletePlugin 外层的 try/catch，删除前直接调用 pluginManager.killPlugin(pluginPath)。同时补了删除路径上的回归测试。