Refactor listener startup error handling

Functions that start listeners (Ranch supervisors) no longer
throw on errors. They simply return the first error encountered
and let the boot step handle it.

Since there is no way for boot steps to indicate errors, this is the
best we can do in this area without a much deeper refactoring of the boot
sequence.

In addition they also log the error. Note that modern Ranch versions
log more reasonable messages when Ranch supervisors exit due to
a listen/bind socket operation error, e.g. when the address/port pair
is already in use.

Closes #1711 (for now), covers #1729 for the server as a drive-by change.

[#160791138]
[#161136615]

0 files changed, 0 insertions, 0 deletions