fix: shuttle init --template, reorder subcommands, fix bugs

[jonaro00]

Description of change

• ⭐ Rename the arguments to init from --axum to -t/--template axum etc
• Reorder cargo-shuttle arguments based on relevance to a new user
• Transparency: showing what cargo init command is being run, and printing the output.
• Rename --new to --create-env
• ⭐ Pass the project name (--name or as prompted) to cargo init --name. This means that the crate name will be what you choose as project name, not what the folder is called. cargo shuttle init --name my-crate -t axum my-shuttle-folder will put "my-crate" in Cargo.toml. Not sure this is the right move. More reading: cargo shuttle init does not handle directory argument properly #665 (comment) https://discord.com/channels/803236282088161321/1076126506323030017/1100716327511015514
• TODO?: Don't prompt for path if it was given as arg. This is kinda tricky because the parsing done by parse_init_path() makes it hard to know if the path was given or not.

⭐= more "breaking" change, happy to discuss

How Has This Been Tested (if applicable)?

• A bunch of manual testing
• The integration tests for init has been updated. Will probably add more. Tests will be updated when template cloning is done.
• The relevant unit test was dumbed down, maybe too much.

New ordering in subcommands

  init        Create a new shuttle project
  run         Run a shuttle service locally
  deploy      Deploy a shuttle service
  deployment  Manage deployments of a shuttle service
  status      View the status of a shuttle service
  stop        Stop this shuttle service
  logs        View the logs of a deployment in this shuttle service
  project     List or manage projects on shuttle
  resource    Manage resources of a shuttle project
  secrets     Manage secrets for this shuttle service
  clean       Remove cargo build artifacts in the shuttle environment
  login       Login to the shuttle platform
  logout      Log out of the shuttle platform
  generate    Generate shell completions
  feedback    Open an issue on GitHub and provide feedback
  help        Print this message or the help of the given subcommand(s)

New help page for init

shuttle ❯ cargo run -p cargo-shuttle -- init --help
Create a new shuttle project

Usage: cargo-shuttle init [OPTIONS] [PATH]

Arguments:
  [PATH]
          Path to initialize a new shuttle project

          [default: .]

Options:
  -t, --template <TEMPLATE>
          Initialize the project with a template

          Possible values:
          - actix-web: Initialize with actix-web framework
          - axum:      Initialize with axum framework
          - poem:      Initialize with poem framework
          - poise:     Initialize with poise framework
          - rocket:    Initialize with rocket framework
          - salvo:     Initialize with salvo framework
          - serenity:  Initialize with serenity framework
          - tide:      Initialize with tide framework
          - thruster:  Initialize with thruster framework
          - tower:     Initialize with tower framework
          - warp:      Initialize with warp framework
          - none:      Initialize with no template

      --working-directory <WORKING_DIRECTORY>
          Specify the working directory

          [default: .]

      --create-env
          Whether to create the environment for this project on shuttle

      --name <NAME>
          Specify the name of the project (overrides crate name)

      --api-key <API_KEY>
          API key for the shuttle platform

  -h, --help
          Print help (see a summary with '-h')

More transparent output from cargo init

A bit whacky, but shows the command and output/warnings/errors from cargo init.

shuttle/test ❯ cargo run -p cargo-shuttle -- init --name xyz -t axum abc
     Running `"cargo" "init" "--bin" "--name" "xyz" "/home/jonaro00/shuttle/test/abc"`
warning: compiling this new package may not work due to invalid workspace configuration

current package believes it's in a workspace when it's not:
current:   /home/jonaro00/shuttle/test/abc/Cargo.toml
workspace: /home/jonaro00/shuttle/Cargo.toml

this may be fixable by adding `test/abc` to the `workspace.members` array of the manifest located at: /home/jonaro00/shuttle/Cargo.toml
Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.
     Created binary (application) package

[oddgrd]

Thanks for this @jonaro00, and thank you for detailing your changes so thoroughly in the PR description, it makes reviewing a joy! I left some small comments but nothing major, this is almost good to go. 🙏

I think the breaking changes to the init commands are fine if we can avoid breaking them again in the upcoming init refactor, but I know from our conversation on Discord that you have considered this. As for the cleanup of the code, LGTM!

We also need to remember to update the docs, readme etc., but we have some time before the next release.

[oddgrd]

Thank you!

[chesedo]

Looking good. Just one comment about a possible improvement.

[oddgrd]

For clarity: I marked this as a breaking change, but it won't break for people who don't upgrade. However, since we also need to update the docs for this it will appear broken for people who follow the docs but haven't updated.

[jonaro00]

@oddgrd Roughly what date is the next release planned? I can change docs before then.
As for the "docs are too new" issue, it seems like "just update to latest" will be the recommended answer to users anyways. (alpha stage)

[oddgrd]

It's planned for monday next week, so if you could swing that it would be great, but if you can't just let me know and I'll do it! And I agree, telling people to upgrade if they encounter this is no biggie. It's just good to try to avoid breaking changes when we can (although we are still very relaxed on this), so users don't always have to upgrade immediately, and also it's good to mark breaking changes clearly so we don't forget when we make a release. 😄

[jonaro00]

@oddgrd
ready for 0.16.0: shuttle-hq/shuttle-docs#91
Some of the examples/showcases on www are getting outdated... If our adventure with token resetting gets around to updating it, I can take a look and bump them too.