Add extra configuration for problem-operator

[dczupryn-dt]

Enable possibility to change settings HIGH_CPU_USAGE_BROKER_SERVICE_NAME and HIGH_CPU_USAGE_FLAG_NAME. That fixes problem with bad name for broker-service deployment.

Before:

2026-01-28T07:33:08.957Z        DEBUG   Feature flag    featureflag/serviceconnector.go:78      Fetching a flag {"flag": "high_cpu_usage"}
2026-01-28T07:33:08.971Z        ERROR   Operator        operator/operator.go:125        An error occurred while updating state for the "high_cpu_usage" flag - failed to fetch the resource for the "high_cpu_usage" flag: failed to get the deployment: deployments.apps "broker-service" not found
2026-01-28T07:33:08.971Z        ERROR   Operator        operator/operator.go:83 An error occurred while updating the state (failed to fetch the resource for the "high_cpu_usage" flag: failed to get the deployment: deployments.apps "broker-service" not found)

After:

2026-01-28T07:30:48.755Z        INFO    Operator        operator/operator.go:100        Updating state...       {"namespace": "easytrade-helm"}
2026-01-28T07:30:48.755Z        DEBUG   Feature flag    featureflag/serviceconnector.go:78      Fetching a flag {"flag": "high_cpu_usage"}
2026-01-28T07:30:48.851Z        INFO    High CPU Usage | Broker Service highcpuusage/brokerservice.go:141       Successfully got the easytrade-broker-service deployment
2026-01-28T07:30:48.851Z        INFO    Operator        operator/operator.go:169        State of the easytrade-broker-service is synchronized {"flag": "high_cpu_usage", "enabled": false}
2026-01-28T07:30:48.861Z        INFO    Operator        operator/operator.go:76 Successfully updated state