docs: update plugin development guide to clarify global vs resource-level plugins

AdminForth/1439/add-global-plugins

Author: yaroslav8765

adminforth/documentation/docs/tutorial/10-Advanced/01-plugin-development.md

@@ -512,7 +512,11 @@ To ensure that plugin activates before some other plugins set `activationOrder`
 
 ## Making plugin global
 
-If you want to make your plugin to be global and add it to the main `index.ts` in `globalPlugins` section, you need to use `pluginsScope: 'global'` and `modifyGlobalConfig` instead of `modifyResourceConfig`:
+Each plugin should define a scope: resource-level or global level. 
+* Resource-level plugins should be used when plugin instance works only with one resource config or it's fields. Instances of resource-scope plugins should be installed into "plugins' field of resource config. 
+* All other plugins should be global-scoped. Such plugins are installed to `globalPlugins` of root adminforth config. They might modify configs of many resources like default AuditLog plugin or use several database resources to store data like default Agent plugin.
+
+To make your plugin global, you need to use `pluginsScope: 'global'` and `modifyGlobalConfig` instead of `modifyResourceConfig`
 
 
 ```ts title="./your-global-plugin/index.ts"

adminforth/index.ts

@@ -296,7 +296,10 @@ class AdminForth implements IAdminForth {
       for (let pluginInstance of resource.plugins || []) {
         afLogger.trace(`🔌 Found plugin: ${pluginInstance.constructor.name} for resource ${resource.resourceId}`);
         if (pluginInstance.pluginsScope === 'global') {
-          throw new Error(formatHugePluginError(`Move plugin ${pluginInstance.constructor.name} to index.ts config.globalPlugins array`));
+          throw new Error(formatHugePluginError(`Please move plugin ${pluginInstance.constructor.name} instance to index.ts config.globalPlugins array.
+            Details: Previously adminforth had only resource-level plugins. To keep project structure clean, in recent version of adminforth we introduced globalPlugins. 
+            Global plugins are installed on whole application and not only one resource (like agent, audit logs etc)
+          `));
         }
         allPluginInstances.push({pi: pluginInstance, resource});
       }