feat: auto-detect chain-prefix from chain binary

[rnbguy]

Closes #97

• Add tests

[andrey-kuprianov]

While a nice-to-have feature per se, it is rushed and unready to be merged at this point; it will create more problems than solve:

• only the prefix is detected, but not denom; this is confusing. The user will have to provide some aspects about the blockchain, but not others. Half automation in this case is actually worse than no automation at all.
• it is unclear how auto-detections works, and should work in general when the prefix can be provided in the chain.toml config file.
• the feature relies on the particular way a binary is expected to react to keys parse 00 --output json. I don't feel this is the standard behavior we should expect of all chains.
• the feature is undocumented. E.g. the transfer tutorial is not adjusted.

First and foremost, it's unclear whether this feature is needed at all from our users. In any case, it is definitely of a low priority. Please postpone working on this feature till after the prototype release, and till we discuss it within the team.

[rnbguy]

only the prefix is detected, but not denom; this is confusing. The user will have to provide some aspects about the blockchain, but not others. Half automation in this case is actually worse than no automation at all.

Denom can be configured in genesis file generation step. It is not exactly hardcoded as chain HRP prefixes.

it is unclear how auto-detections works, and should work in general when the prefix can be provided in the chain.toml config file.

We can still keep prefix key in chain.toml and update it when binary is updated (via atomkraft chain binary junod)

the feature relies on the particular way a binary is expected to react to keys parse 00 --output json. I don't feel this is the standard behavior we should expect of all chains.

I agree with the fact that we should not use a feature that is not supported by cosmos-SDK by default. I opened a PR at cosmos-sdk. But I don't expect it to be present in any other chains soon.

the feature is undocumented. E.g. the transfer tutorial is not adjusted.

I wait for an initial code review to add tests and update tutorials. Because it doesn't make sense if a PR is rejected.