[yugabyted] Starting yugabyted with client cert auth enabled doesn't work

[iSignal]

Jira Link: DB-14929

Description

Start a yugabyted single node cluster with

sanketh@varahivm yugabyte-db > cache_logging > bin/yugabyted start --secure --tserver_flags="ysql_hba_conf_csv={hostssl all all all md5 clientcert=verify-full}" --ui false

or

sanketh@varahivm yugabyte-db > cache_logging > bin/yugabyted start --secure --tserver_flags="ysql_hba_conf_csv={hostssl all all all md5 cert}" --ui false

This fails when yugabyted attempts to connect to the YSQL port

Starting yugabyted...
✅ YugabyteDB Started
| Enabling Encryption in Transit and Password Authentication...Could not update Postgress user password. Exception: Traceback (most recent call last):
  File "/home/sanketh/code/yugabyte-db/bin/yugabyted", line 5617, in update_db_passwords
    try:
  File "/home/sanketh/code/yugabyte-db/bin/yugabyted", line 10489, in retry_op_with_argument
RuntimeError: Failed after retrying operation for 60.3484206199646 secs.

yugabyted needs to either use the local socket or generate client certificates. Generating client certs is better given the user can also use them to connect in this case.

Warning: Please confirm that this issue does not contain any sensitive information

• I confirm this issue does not contain any sensitive information.