feat: compile chain binary from remote

[rnbguy]

Closes #111

Example usage,

atomkraft init transfer
cd transfer
atomkraft chain remote gh:cosmos/cosmos-sdk --ref v0.45.8
...
atomkraft test trace ...

[andrey-kuprianov]

As in #98, I have essentially the same comments.

• It is unclear at all whether this feature is needed by our users. We should first discuss with the users, and with our PO (@tesnimab), whether this is needed.
  • I suppose that actually most of our users simply will want to use some binary that is already present on their machines (dev version, not yet released on the main repo)
• I can imagine lots of situations when it won't work at all:
  • if the project is compiled not using make build (e.g. some custom build process)
  • if there are multiple executables produced
• The implementation is rushed, and I suppose there are cases where it will work not as expected
  • e.g. , I am not particularly fond of including things like glob("*/*") into our codebase. It may have many unforeseen consequences

Besides, we are in the feature freeze now, before the prototype release, so no new features should be added. Please postpone working on that till the prototype release.

[rnbguy]

I need this feature to write tests for methods used in chain subcommand.

If this PR is rejected, I will still need it. I will put it somewhere like test.utils in that case.

---

It is unclear at all whether this feature is needed by our users. We should first discuss with the users, and with our PO (@tesnimab), whether this is needed.

It is targeted for CI capabilities.

I can imagine lots of situations when it won't work at all:

The implementation is rushed, and I suppose there are cases where it will work not as expected

It is not the exclusive way to set up chain binary. atomkraft chain remote is an alternative to atomkraft chain binary.

if the project is compiled not using make build (e.g. some custom build process)
if there are multiple executables produced

I agree with this. But this works for most cosmos-sdk chain binary.

e.g. , I am not particularly fond of including things like glob("/") into our codebase. It may have many unforeseen consequences

Did you mean a long runtime to loop glob("*/*")? Notice, I only search for files till depth 2.