ICT should give more descriptive errors when chain genesis validation fails

[dowlandaiello]

It would be helpful if local-ic was able to report more detailed errors when, for example, a parameter in the chain genesis JSON is incorrectly spelled or misplaced. Currently, this results in a bizarre, ambiguous error unrelated to the genesis at all, and the only way to determine the source of the error is by looking through the killed docker container's logs.

Example incorrect chain genesis param:

{
          "key": "app_state.gov.params.deposit_period",
          "value": "3s
},

Example current error:

2024-08-30T17:03:43.787Z        FATAL   interchain/start.go:176 ic.Build        {"error": "failed to start chains: failed to start chain localosmosis-1: All attempts fail:\n#1: post failed: Post \"http://0.0.0.0:26659\": dial tcp 0.0.0.0:26659: connect: connection refused\n#2: post failed: Post \"http://0.0.0.0:26659\": dial tcp 0.0.0.0:26659: connect: connection refused\n#3: post failed: Post \"http://0.0.0.0:26659\": dial tcp 0.0.0.0:26659: connect: connection refused\n#4: post failed: Post \"http://0.0.0.0:26659\": dial tcp 0.0.0.0:26659: connect: connection refused\n#5: post failed: Post \"http://0.0.0.0:26659\": dial tcp 0.0.0.0:26659: connect: connection refused\n#6: post failed: Post \"http://0.0.0.0:26659\": ..................

This is not necessarily a bug or anything, but it would be nice if the error from inside the docker container could be bubbled up to local-ic somehow!

[Reecepbcups]

Agree!

Currently Interchaintest does not read / parse panics in a proper way to show the user. I had an issue on this, unsure where it went. Once a panic parser is in ICT this will be automatically added to local-ic as well due to how it is designed.

Also ref:

• fail to create key error is deceiving on start #942

[Reecepbcups]

PR is up and pending review from our side. It will parse out any panics on startup, return this error, show all the logs, and cleanup any containers hanging.