add a flag to reflex run that will ignore ssl error self signed cetificate

[david-thrower]

On many early - stage projects, I will use self - signed / staging ACME certificates, using [ipaddress].xip.io, [ipaddress].sslip.io, [ipaddress].nip.io, ... as a placeholder domain.

This I do with good reason:

• To avoid unnecessary domain registrations, traffic with ACME, and in some cases, failed acme challenges for things that are inherently ephemeral and only being used for temporary / fly -by - night development hosts.
• Since I generated the certificate and recognize it, I can easily confirm that I am communicating with the right host and not a man in the middle.
• It allows me to validate that the app works, the pod networking, Ingress, and Service configurations are correct, ... before I register a real domain for a permanent staging or production cluster, configure an external DNS, ... etc.

With that said:

This will of course create a self signed cert warning on a browser, which is not a problem. Since no real user is logging in, I can just acknowledge that I recognize and trust the host and proceed, but even if I do, the web-socket traffic won't make it through, unless I set API_URL to HTTP://[ipaddress].sslip.io not HTTPS://[ipaddress].sslip.io argument (in v0.4.4). In 0.4.5, even if I do set the API_URL to an HTTP://[ipaddress].sslip.io not HTTPS://[ipaddress].sslip.io, the websocket traffic it appears that it isn't making it through (#2935 ).

I think that it may be a solution if:

• A separate flag could be added to reflex run that when set, will ignore SSL errors associated with self signed certs in the connection with the websocket API.
• SSL errors could be ignored if in DEBUG mode (Would fix this, but probably not the safest option)