feat: Don't use "%FLOW_PATH_ROOT%" as default group name

A common deployment strategy might involve creating arbitrarily named
deployment target folders, installing a new flow instance, warming up
caches and either switching symlinks or web server web root settings
to that new directory.

Using %FLOW_PATH_ROOT% as default supervisor group name will result in
constantly eliminating whole supervisor groups and creating new ones
on every deployment, although most of the time the supervisor config
remains nearly unchanged.

Configuration/Settings.yaml

@@ -9,10 +9,18 @@ Netlogix:
     groups:
 
       default:
-        # Supervisor group name.
-        # Defaults to the array key if not present.
+        # Maps to a Supervisor group name.
         # Gets cleaned up to not contain invalid characters as of supervisor settings
-        name: "%FLOW_PATH_ROOT%"
+        #
+        # In general, `supervisorctl restart default:` calls are limited to only one
+        # specific group.
+        # If multiple flow instances share a common supervisor daemon, the unique group name
+        # per flow instances allows restart calls on deployment that don't affect other flow
+        # instances.
+        # This can be changed to e.g. `name: "%FLOW_PATH_ROOT%"`
+        #
+        # Defaults to the array key if not present.
+        name: "default"
 
         # Defaults to 999
         priority: 100