Updating terminated TLS listener may leak sensitive data in logs for task_flow

When creating a terminated TLS listener, the certificate, private key and passphrase might be leaked to the worker.log

We found those information as the taskflow was transitioning from RUNNING to FAILURE and the atoms were logged with

2023-07-24 14:00:43.380 1784274 WARNING octavia.common.base_taskflow [ ] Task 'octavia.controller.worker.v2.tasks.amphora_driver_tasks.ListenersUpdate' ([...]) transitioned into state 'FAILURE' from state 'RUNNING'
3 predecessors (most recent first):
  Atom 'octavia.controller.worker.v2.tasks.database_tasks.MarkHealthMonitorPendingCreateInDB' {'intention': 'EXECUTE', 'state': 'SUCCESS', 'requires': {'health_mon': {'admin_state_up': True, 'delay': 3, 'expected_codes': '200', 'healthmonitor_id': '[...]', 'http_method': 'GET', 'max_retries': 3, 'max_retries_down': 3, 'name': '[...]', 'pool_id': '[...]', 'timeout': 3, 'type': 'HTTPS', 'url_path': '/healthcheck', 'http_version': 1.0, 'domain_name': None, 'project_id': '[...]'}}, 'provides': None}
  |__Atom 'octavia.controller.worker.v2.tasks.lifecycle_tasks.HealthMonitorToErrorOnRevertTask' [...]

Leaked data in this atom and below, e.g. all information in default_tls_container_data should be considered confidential