Refactor Config class, separating its responsibilities into PortalConfig and ConfigLoader

[mosoriob]

The Config class is currently handling multiple responsibilities, including:

• Managing the portal.properties file data structure
• Handling permission validation, such as checkDomain, dynamic user configuration setup, and viewerID management.

To improve maintainability and readability, we should separate these responsibilities into separate classes or functions. This will make the code easier to understand and modify in the future.

Proposed Solution

Create two new classes:

• Config to handle the portal.properties file data structure
• ConfigLoader to handle permission validation and dynamic configuration

Benefits

• Improved readability and maintainability of the codebase
• Clear separation of concerns for better organization
• Easier testing and debugging of individual components

[mosoriob]

ok