Feature/rflib development mode

[j-fischer]

Introduce Development Mode for Internal UI Component Logging in RFLIB

---

Description

Introducing a new Development Mode feature that adjusts the logging behavior of RFLIB's internal UI components, specifically those used in the Ops Center. The feature is controlled via a new global configuration setting, RFLIB_Development_Mode_Enabled.

Key Changes

1. Global Configuration Setting:

   • API Name: RFLIB_Development_Mode_Enabled
   • Purpose: Controls the log level of the rflib_LoggerUtil.logInternal() methods.
   • When set to TRUE, log statements in internal UI components will use the INFO level.
   • When set to FALSE, log statements will default to the DEBUG level.
   • Default Value: FALSE
   • Recommended Usage:
     • Enable only during development of new components for RFLIB's Ops Center.
     • Use for debugging UI-related issues in RFLIB.

2. Updates to rflib_LoggerUtil:

   • Added two new utility methods:
     • logInternal(rflib_Logger logger, String message)
     • logInternal(rflib_Logger logger, String message, Object[] args)
   • These methods dynamically adjust the log level (INFO or DEBUG) based on the RFLIB_Development_Mode_Enabled setting.

3. Refactoring of Affected Controllers:

   • Updated all log statements of type INFO and DEBUG in the following controllers to use the new logInternal methods:
     • rflib_ApexJobSchedulerController
     • rflib_CustomSettingsEditorController
     • rflib_LogEventViewerController
     • rflib_PermissionsExplorerController
     • rflib_PublicGroupMemberManagerController
     • rflib_UserPermAssignmentController
     • rflib_UserPermSetManagerController
     • rflib_UserProfileResolverController

---

Why This Feature?

• Provides better control over logging during development and debugging phases.
• Reduces unnecessary log noise in production environments while maintaining flexibility for internal debugging.