Add enablefilelogger to CostVolumePro Web API Manager

Feature Request: Add enableFileLogger parameter to Cost Volume Pro Web API Manager

Summary:
Introduce an enableFileLogger configuration parameter to the Cost Volume Pro Web API Manager, along with the necessary supporting configuration entries, so that file-based logging can be enabled and managed consistently—similar to existing implementations in BOE PRO and Auth Pro.

Problem Statement:
Currently, the Cost Volume Pro Web API Manager does not support an enableFileLogger option in its configuration. As a result, teams must manually modify the Web API App Settings file after each deployment to configure logging. This manual step is repetitive, error-prone, and does not align with existing patterns used in BOE PRO and Auth Pro, leading to inconsistent logging behavior and additional overhead during deployments.

Proposed Solution:
Add an enableFileLogger parameter to the Cost Volume Pro Web API Manager configuration, with behavior and structure consistent with BOE PRO and Auth Pro.
Automatically generate or update the appropriate Web API App Settings entries when enableFileLogger is enabled, eliminating the need for manual file edits post-deployment.
Ensure that the logging configuration (paths, levels, rotation/retention settings as applicable) can be managed via standard deployment and configuration mechanisms rather than direct file manipulation.
Maintain backward compatibility so existing deployments without this parameter continue to function as they do today.

Benefits:
Reduces manual configuration effort during deployments by eliminating post-deployment file edits.
Improves consistency across products (Cost Volume Pro, BOE PRO, Auth Pro) by standardizing how file logging is enabled and managed.
Decreases the risk of misconfiguration and related logging gaps or failures.
Speeds up deployment workflows and increases reliability for operations teams managing multiple environments.