Use chia cli parser

[altendky]

Draft for:

• Handle the --help case.
  • https://replit.com/@altendky/TurbulentFelineDaemon-2#main.py
• Self reflection over night.
• Handle the -h case.
• Drop PyPy testing in test: stop testing pypy #125
• Probably copy in and license acknowledge. With some decisions about how to inspect we could then handle multiple chia versions.

[ericaltendorf]

This is great!

[altendky]

Note that this is still hand waving in terms of the subcommand parsing. There could be arguments interleaved for parent subcommands in the command line without making it so that it isn't a plot command (present code would ignore such a process). There may be more but at at least venv/bin/chia --root-path my_path_to_chia_stuff plots create should be valid. But, I think it's fair to leave that for 'maybe later'. Also, the choice of -h and --help is hard coded since command.get_help_option_names(ctx=context) only returns --help (comment left in the relevant code). I didn't dig hard into the details of that.

[chelseadole]

Looks good to me :)

[altendky]

This got reworked to copy in the Chia command parsing code rather than having the dependency on the chia-blockchain package. In various cases people are installing chia without the Python package such as .dmg on macOS. This approach also allows us to store multiple versions and in the future we could attempt to identify the version of the process and pick the proper parsing code for it. Anyways... maybe this is ready for real review and merging so we can move on from all these complaints...

[ericaltendorf]

It seems unfortunate that we need to copy chia code over, but if that's what seems like the best option, let's go for it. Should it be documented somewhere what's going on? I.e., which code came from chia and what the process should be for updating it / keeping it in sync?

[altendky]

Alrighty, there's some documentation. Let me know if it is clear.

[ericaltendorf]

Makes sense, thanks!