Error on module init is not printed

[ersonp]

Describe the bug
The error returned during the initialization of a module is not printed as well as the logs print that the module is successfully initialized. But if other modules are dependent on the errored module then they will forever wait for that module. And because of no error logs it becomes hard to find the issue.

Environment information:

• OS: e.g. Linux
• Platform: Linux 5.13.0-39-generic x86_64

Steps to Reproduce
Steps to reproduce the behavior:

1. Add this log v.log.Error(err) before this line
2. Build make build
3. Make two configs with ./skywire-cli config gen -irt
4. Run hypervisor A sudo ./skywire-visor -c skywire-config.json
5. On new terminal Run hypervisor B sudo ./skywire-visor -c skywire-config2.json
6. See the error

Actual behavior
Hypervisor B

[2022-04-20T20:35:34+05:30] ERROR [visor]: listen tcp 127.0.0.1:3435: bind: address already in use
[2022-04-20T20:35:34+05:30] INFO [dmsg_pty]: Initialized in 227.306µs (409.348µs with dependencies)
[2022-04-20T20:35:34+05:30] INFO [cli]: Initialized in 543.949µs (544.22µs with dependencies)

In the logs in hypervisor B where the error listen tcp 127.0.0.1:3435: bind: address already in use is returned by the module but without our log there is no indication of the error. The logs show that the cli module has initialized without any issue but this causes the visor module to not initialize as it is still waiting for the cli module to initialize without any error.