chore: remove katana leftover

[kariy]

Summary by CodeRabbit

• Chores
  • Removed the Katana CLI binary and all related command-line features, including chain initialization, configuration, database utilities, and slot paymaster management.
  • Deleted support for interactive prompts and settlement chain integration.
  • Eliminated the ability to generate shell completion scripts.
  • The Katana CLI is no longer available as part of the application.

[coderabbitai]

Walkthrough

Ohayo sensei! This change completely removes the Katana binary crate and all of its associated CLI modules, source files, and configuration files from the codebase. The deletion encompasses the main entry point, command-line interface logic, initialization utilities, database and configuration commands, settlement contract deployment and verification routines, slot paymaster management, and all related feature flags and dependencies. As a result, all public entities, structs, functions, and CLI functionalities tied to the Katana binary are eliminated.

Changes

Files / Paths	Change Summary
bin/katana/Cargo.toml	Deleted the Cargo manifest, removing all package metadata, dependencies, and feature declarations for Katana binary.
bin/katana/src/main.rs	Deleted the main entry point for the Katana CLI application.
bin/katana/src/cli/mod.rs bin/katana/src/cli/config.rs bin/katana/src/cli/db.rs	Deleted the CLI module, including command parsing, subcommands (config, db, completions), and their execution logic.
bin/katana/src/cli/init/mod.rs bin/katana/src/cli/init/prompt.rs bin/katana/src/cli/init/deployment.rs bin/katana/src/cli/init/settlement.rs bin/katana/src/cli/init/slot.rs	Deleted all initialization modules, including interactive prompts, settlement contract deployment, slot paymaster management, and related utilities.

Possibly related PRs

• fix(katana): ensure paymaster accounts are unique #3017: Modified the prompt function for paymaster uniqueness, which is now deleted in this PR.
• refactor(cli): katana cli module  #2236: Introduced and refactored the Katana CLI module and subcommands, all of which are removed here.
• feat: bump cairo 2.10 and remove katana and torii dependencies #3169: Also removes the Katana binary and associated crates from the workspace, reflecting the same removal focus as this PR.

Suggested reviewers

• glihm

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 41b919c and d1c25f8.

📒 Files selected for processing (10)

• bin/katana/Cargo.toml (0 hunks)
• bin/katana/src/cli/config.rs (0 hunks)
• bin/katana/src/cli/db.rs (0 hunks)
• bin/katana/src/cli/init/deployment.rs (0 hunks)
• bin/katana/src/cli/init/mod.rs (0 hunks)
• bin/katana/src/cli/init/prompt.rs (0 hunks)
• bin/katana/src/cli/init/settlement.rs (0 hunks)
• bin/katana/src/cli/init/slot.rs (0 hunks)
• bin/katana/src/cli/mod.rs (0 hunks)
• bin/katana/src/main.rs (0 hunks)

💤 Files with no reviewable changes (10)

• bin/katana/Cargo.toml
• bin/katana/src/main.rs
• bin/katana/src/cli/config.rs
• bin/katana/src/cli/init/prompt.rs
• bin/katana/src/cli/db.rs
• bin/katana/src/cli/mod.rs
• bin/katana/src/cli/init/slot.rs
• bin/katana/src/cli/init/mod.rs
• bin/katana/src/cli/init/deployment.rs
• bin/katana/src/cli/init/settlement.rs

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.