Simplify marker file recreation logic on plugin deletion

Refactored the process for recreating the marker file when a plugin directory is not fully deleted. Removed unnecessary try-catch and nested checks, now directly checking for file existence and creating it if missing. This streamlines the code and removes redundant error handling.

Author: Jack251970

Flow.Launcher.Core/Plugin/PluginConfig.cs

@@ -35,17 +35,10 @@ public static List<PluginMetadata> Parse(string[] pluginDirectories)
                         if (!fullyDeleted)
                         {
                             // Directory was not fully deleted, recreate the marker file so deletion will be retried on next startup
-                            try
+                            var markerFilePath = Path.Combine(directory, DataLocation.PluginDeleteFile);
+                            if (!File.Exists(markerFilePath))
                             {
-                                var markerFilePath = Path.Combine(directory, DataLocation.PluginDeleteFile);
-                                if (!File.Exists(markerFilePath))
-                                {
-                                    File.WriteAllText(markerFilePath, string.Empty);
-                                }
-                            }
-                            catch
-                            {
-                                // If we can't create the marker file, at least log the warning
+                                File.WriteAllText(markerFilePath, string.Empty);
                             }
                             PublicApi.Instance.LogWarn(ClassName, $"Directory <{directory}> was not fully deleted. Some files or folders may still remain. Deletion will be retried on next startup.");
                         }