Current uses of bundled cargo (three subtasks):

• cargo-shuttle - Done Remove cargo from cargo shuttle #765
  • When using shuttle init. This can be replaced with a Command call.
  • ToSemver when checking versions of cargo-shuttle and runtime. This is not strictly needed, a == is probably sufficient. (or just semver crate)
• deployer - Done feat: show output of failed tests #907
  • CliError is used when pre deploy testing. (can be replaced)
  • Various enums and config struct used to construct the test command. All options used are easily used from CLI args.
• service part 1 - Done feat(service): get rid of cargo dependency #922
  • is_next and ensure_{bin,cdylib}: can be done through cargo_metadata.
  • clean_crate: should be easily done with a command.
• service part 2 - Done feat(service): get rid of cargo dependency #922
  • get_config: gets cargo config, but is never modified before use, so it is not needed if bundled cargo is not used.
  • get_compile_options: uses standard CLI options. (minor TODO here is to not limit cpus to 4 on local release run)
  • check_no_panic: could be done by parsing toml i guess... (main challenge here is that cargo config is nightly) -- can probably be dropped instead [Enhancement]: Get rid of cargo dependency #756 (comment)
  • build_workspace: figure out another way to find the crates of the workspace, as well as getting the data we need for the BuiltService struct.

All done 🥳