ca.framework.cert.management.custom.san and "cloudstack-setup-databases -i" force a single string which must be a hostname

### problem

I need to add 127.0.0.1 to the certificate for $IP:9090/ and ca.framework.cert.management.custom.san is the way to do it, but the feature interprets the entry as a single string, such that the following value:
_cloudstack.internal, 127.0.0.1_

leads to this kind of alt name configuration:

_~# openssl s_client -connect 127.0.01:9090 /dev/null | openssl x509 -noout -text | grep DNS:
IP Address:192.168.0.123, DNS:**cloudstack.internal, 127.0.0.1**_

Note that "cloudstack.internal, 127.0.0.1" is a single string here, so the comma separation is not a thing as I assumed.

Replacing cloudstack.internal with 127.0.0.1 takes me one step further, in that 127.0.0.1 is added to the alt names, but is treated as a hostname, not an IP.

_~#openssl s_client -connect 127.0.01:9090 /dev/null | openssl x509 -noout -text | grep DNS:
IP Address:192.168.0.123, DNS:127.0.0.1_

To further aggravate me, even _cloudstack-setup-databases -i 127.0.0.1_ produces the same results, 127.0.0.1 is treated as hostname, not IP, just like the above.

### versions

4.21.0.0 KVM

### The steps to reproduce the bug

_No response_

### What to do about it?

_No response_

Comienza reproduciendo el comportamiento del certificado con ca.framework.cert.management.custom.san y cloudstack-setup-databases -i 127.0.0.1 en la configuración KVM 4.21.0.0 indicada. Inspecciona el certificado con openssl s_client y openssl x509 como se muestra; se considera terminado cuando los valores SAN se analizan correctamente, con las direcciones IP representadas como entradas IP en lugar de nombres de host y los valores múltiples tratados de forma distinta.

Escrito por el modelo de indexación a partir del texto del issue.