[Refactor] Split code into separate files for better organization/maintainability

[AliSoftware]

Note

This PR builds on top of #11

What

Just moving the code around to spread it in dedicated commands/*.rs files for better organization.

The diff is mostly just code being cut-and-pasted from one place to another (mostly from main.rs to the relevant commands/*.rs) without change (except adjusting the use imports and the like).

Detail of moved code

• Moved fn cmd_init + init_instructions from main.rs to commands/init.rs
• Moved fn cmd_unlock from main.rs to commands/unlock.rs
• Moved fn cmd_lock from main.rs to commands/lock.rs
• Moved fn cmd_status from main.rs to commands/status.rs, alongside the related types that were in status.rs before (struct RepositoryStatus, struct FileStatus, struct FileStatusList)
• Moved fn cmd_key_show + cmd_key_rotate + confirm + rotate_confirmation_prompt + rotate_instructions from main.rs to commands/key.rs
• Moved filter.rs to commands/filter.rs (content unchanged)
• Kept in main.rs only:
  • The enum declarations for the commands and subcommands (enum Commands, enum KeyCommands, enum FilterCommands
  • The command dispatch logic in fn main() { match cli.command … } that tells which cmd_* method to call for each command being matched during CLI parsing
  • I also removed the fn cmd_key and fn cmd_filter methods—that were doing the dispatch for the corresponding subcommands—to instead inline them as a nested match inside the fn main() dispatch logic

Why

As the code is growing, this split makes the codebase more readable and maintainable IMHO, with clearer separation of what each *.rs file is about.

For example, before this change, it wasn't clear that a file like filter.rs contained code related to handling the filter subcommands, but key.rs was NOT about handling the key subcommands—but instead a file containing model objects and business logic to manipulate Key objects. With this reorg, it's clearer that anything under commands/*.rs is for handling commands and subcommands, while the rest of the model objects and business logic is outside this new commands module.

Testing

Since this is just code being moved, the behavior shouldn't change. So as long as CI (which runs cargo check, cargo clippy, and cargo build) passes, we should be OK.

If you really want to validate the behavior of the tool hasn't changed, feel free to run cargo build --release from this PR's branch, add <path/to/this/repo>/target/release to your $PATH, then play around with PRs already implementing git-conceal like woocommerce/woocommerce-android#14979 or Automattic/pocket-casts-android#4841

[iangmaia]

Nice work 👏 I tested it by recompiling and running the main commands just in case, everything still looking good 👍