Improve error reporting for listeners that fail to start #1711
Description
Currently when a listener failed to start an error record from a supervisor will be spit out to the user, e.g.
{"Kernel pid terminated",application_controller,"{application_start_failure,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{{case_clause,{error,{{shutdown,{failed_to_start_child,{ranch_listener_sup,{acceptor,{0,0,0,0,0,0,0,0},5671}},{shutdown,{failed_to_start_child,ranch_acceptors_sup,{listen_error,{acceptor,{0,0,0,0,0,0,0,0},5671},no_cert}}}}}
…
which is not very useful to most users.
A more specific message that says a listener failed to start because of error so and so (in this case, no_cert which might also be formatted for common scenarios) would be a welcome improvement.