Add host parameter to telemetry config

[andynog]

Closes: #1032

Description

Add host parameter to telemetry config section, to allow access from a different machine in the network (eg. by using 0.0.0.0 as the host).

---

For contributor use:

• Updated the Unreleased section of CHANGELOG.md with the issue.
• If applicable: Unit tests written, added test to CI.
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Updated relevant documentation (docs/) and code comments.
• Re-reviewed Files changed in the Github PR explorer.

[andynog]

lgtm, the only suggestion is that if a more meaningful message could be added when exiting. The message "Address in use" does not have a context and for an operator is not helpful because it doesn't say the telemetry server failed to start because it's trying to use a port which is already allocated. If there's a way to at least say telemetry server or something like that I think that would be helpful than just bubbling up the error from the web server

Error: Hermes failed to start, last error: Address already in use (os error 48)

[romac]

It says right before exiting with this message:

Jun 02 22:32:48.130 ERROR ibc_relayer_cli::commands::start: telemetry service failed to start: Address already in use (os error 48)

which is not perfect but at least provides some more context. Is that enough or would you want it to also mention this in the final error? Maybe we could introduce an enum to capture the server error and then print it accordingly?

[andynog]

It says right before exiting with this message:

Jun 02 22:32:48.130 ERROR ibc_relayer_cli::commands::start: telemetry service failed to start: Address already in use (os error 48)

which is not perfect but at least provides some more context. Is that enough or would you want it to also mention this in the final error? Maybe we could introduce an enum to capture the server error and then print it accordingly?

It says right before exiting with this message:

Jun 02 22:32:48.130 ERROR ibc_relayer_cli::commands::start: telemetry service failed to start: Address already in use (os error 48)

which is not perfect but at least provides some more context. Is that enough or would you want it to also mention this in the final error? Maybe we could introduce an enum to capture the server error and then print it accordingly?

Sorry, my bad. Indeed it says. I thought that ERROR line was only shown depending on the log_level parameter in the config but that's not the case, it will show in any case. So that's all good.

Thanks!