Allow blank DB host value, reuse backend code

[AlanCoding]

SUMMARY

This avoids us create a "connection string" which was already believed to be brittle and undesirable.

Here are some research links of various value:

https://github.com/django/django/blob/main/django/db/backends/base/base.py#L30

https://github.com/django/django/blob/main/django/db/backends/postgresql/base.py

This create the same thing as django.db.connection, but using that object specifically comes with a lot of baggage. It's much cleaner to just create it, as what we need is set up in its __init__. This avoids touching the already active connection, which is being used for other stuff. The deepcopy we already had still seems like a good idea.

The idea is that "HOST" in the DATABASES setting may be an empty string. Instead of handling this specifically, I'm trying to do it the "right" way finally here. Presumably this works for password-less auth which we were already trying to allow.

Essentially, we have to "translate" the Django database settings into the psycopg parameters, and instead of doing it manually we will use the logic already written in Django.

ISSUE TYPE

• Bug, Docs Fix or other nominal change

COMPONENT NAME

• API

[AlanCoding]

Still trying to get more test results before merging, which will have to wait until the dependencies are fixed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud