[AB-73] adding different feature modes to define whether or not certain actions should be logged, changing name of setup, disable and enable command to show that they are supposed to be for features

abstracto-application/abstracto-modules/modmail/modmail-impl/src/main/java/dev/sheldan/abstracto/modmail/setup/InvalidCategoryException.java

@@ -14,7 +14,7 @@ public class InvalidCategoryException extends AbstractoRunTimeException implemen
 
     @Override
     public String getTemplateName() {
-        return "setup_category_not_valid_exception";
+        return "feature_setup_category_not_valid_exception";
     }
 
     @Override

abstracto-application/abstracto-modules/modmail/modmail-impl/src/main/java/dev/sheldan/abstracto/modmail/setup/ModMailCategoryDelayedActionConfig.java

@@ -23,7 +23,7 @@ public class ModMailCategoryDelayedActionConfig implements DelayedActionConfig {
 
     @Override
     public String getTemplateName() {
-        return "setup_modmail_category_action";
+        return "feature_setup_modmail_category_action";
     }
 
     @Override

abstracto-application/abstracto-modules/modmail/modmail-impl/src/main/java/dev/sheldan/abstracto/modmail/setup/ModMailCategorySetupBean.java

@@ -73,7 +73,7 @@ public class ModMailCategorySetupBean implements ModMailCategorySetup {
      */
     @Override
     public CompletableFuture<SetupStepResult> execute(AServerChannelUserId user, SetupStepParameter parameter) {
-        String messageTemplateKey = "setup_modmail_category_message";
+        String messageTemplateKey = "feature_setup_modmail_category_message";
         SetupModMailCategoryMessageModel model = SetupModMailCategoryMessageModel
                 .builder()
                 .build();