Move Email and Webhook Settings to Application Configuration

Feature Request: Move Email and Webhook Settings to Application Configuration

Summary:
Move email and webhook settings from the user interface into an application-level JSON configuration file so sensitive values are managed securely and are not visible to all users. This change should centralize configuration management while reducing unnecessary exposure of sensitive system settings.

Problem Statement:
Currently, email and webhook settings are available in the UI, which makes sensitive configuration information accessible to users who should not have visibility into it. This creates a security and governance concern, especially when these settings contain credentials, endpoints, or other system-level details. It also increases the risk of accidental changes or misuse by users who do not need direct access to these values.

Proposed Solution:
Store email and webhook settings in an application setting JSON file instead of exposing them in the UI.
Restrict access to these settings so they can only be managed through secure application configuration processes.
Ensure the application reads and applies the JSON-based settings reliably at runtime.
Remove or limit the corresponding UI fields so non-authorized users cannot view or modify sensitive values.
Provide clear validation and error handling for malformed or missing JSON configuration values to avoid runtime issues.

Benefits:
Improves security by limiting exposure of sensitive email and webhook configuration details.
Reduces the risk of unauthorized access or accidental changes in the UI.
Centralizes configuration management for easier administration and consistency across environments.
Supports better governance by separating user-facing functionality from application-level system settings.