BUG: IP Address Formatting in DB

On our catch up call, @SimonLab noted that the IP addresses are not being stored correctly.

```sh
flyctl postgres connect -a hits-db
```

```sh
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
0.0.0.0.0.65535.47400.59506
--More--
```

Ref: https://en.wikipedia.org/wiki/0.0.0.0


I suspect this might be a Fly.io thing ...

# Todo

+ [ ] Investigate why the IP addresses aren't being stored correctly by _briefly_ logging them to `sdout` (`IO.inspect`) so that we can simply tail the logs and see if the issue is at the database level.
+ [ ] Report back your findings!

Start with the `flyctl postgres connect -a hits-db` entry point to inspect the stored values, then add the requested brief `IO.inspect` logging before persistence and tail the logs. Done means reporting whether the malformed IP address is produced before reaching the database or introduced at the database level.

Written by the indexing model from the issue text.