This section details on the original issue you should resolve

<issue_title>commands/db: Fix RecycleCleanCommand critical bugs and performance issues</issue_title>
<issue_description>## 🐛 Bug Description

The RecycleCleanCommand has several critical issues that prevent it from functioning correctly and provide poor user experience:

1. Critical Database Access Bug

• Issue: Uses open_rooch_db_readonly() instead of open_rooch_db() for deletion operations
• Impact: Command fails at runtime when attempting to delete data in read-only database mode
• Location: crates/rooch/src/commands/db/commands/recycle_bin.rs:574-579

2. Inconsistent Logging

• Issue: Mixed usage of eprintln! and println! throughout the command
• Impact: Poor user experience, inconsistent with codebase standards
• Examples: Line 564 uses eprintln! for errors, Line 654 uses eprintln! for user prompts

3. Manual Input Handling

• Issue: Uses manual std::io operations instead of existing utility functions
• Impact: Poor error handling, inconsistent with other commands
• Location: crates/rooch/src/commands/db/commands/recycle_bin.rs:654-663

4. Suboptimal Performance for Full Cleanup

• Issue: Uses O(N) batch deletion even when deleting all entries
• Impact: Inefficient when clearing the entire recycle bin
• Opportunity: O(1) column family drop for full cleanup scenarios

🎯 Proposed Solution

Phase 1: Critical Bug Fixes

1. Fix Database Access: Replace open_rooch_db_readonly() with open_rooch_db()
2. Standardize Logging: Replace all print statements with structured tracing macros
3. Use Standard Input Handling: Replace manual input with utils::prompt_yes_no()

Phase 2: Performance Optimization

4. Hybrid Deletion Strategy:
   • O(1) deletion when no filters specified (drop column family)
   • O(N) deletion when selective filters are used (batch deletion)

📊 Performance Impact

🛠 Implementation Details

Database Access Fix

// Current (BROKEN):
let (_root_meta, rooch_db, _start) = open_rooch_db_readonly(/*...*/);

// Fixed:
let (_root_meta, rooch_db, _start) = open_rooch_db(/*...*/);

Hybrid Deletion Strategy

pub fn delete_entries(&self, filter: &RecycleFilter, batch_size: usize) -> Result<usize> {
    // Check if this is a "delete all" operation
    if self.is_delete_all(filter) {
        tracing::info!("Deleting all recycle bin entries - using optimized column family drop");
        return self.drop_and_recreate_column_family();
    }
    
    // Use batch deletion for selective operations
    self.batch_delete_with_filter(filter, batch_size)
}

Standardized Logging

// Replace all println!/eprintln! with:
tracing::info!("User-facing messages");
tracing::error!("Error messages");
tracing::warn!("Warning messages");

Standard Input Handling

// Replace manual input with:
if !self.answer_yes && !utils::prompt_yes_no("Are you sure you want to permanently delete all entries matching the specified criteria?") {
    tracing::info!("Operation cancelled by user.");
    return Ok(None);
}

🧪 Testing Strategy

1. Unit Tests: Test both deletion strategies with various filter combinations
2. Integration Tests: Test with actual database operations
3. Edge Cases: Empty recycle bin, different filter conditions
4. Performance Tests: Verify O(1) vs O(N) behavior for different scenarios

🔒 Safety Considerations

• Preserve existing safety checks: --dry-run and --force requirements remain
• Maintain confirmation prompts: User approval still required for destructive operations
• Add operation logging: Clear logging of which strategy is being used
• Error handling: Proper error handling for column family operations

📝 Files to Modify

Primary Files

• crates/rooch/src/commands/db/commands/recycle_bin.rs - Main implementation fixes
• crates/rooch-pruner/src/recycle_bin.rs - Hybrid deletion strategy

Reference Files

• crates/rooch/src/utils.rs - Utility functions to use
• moveos/moveos-store/src/state_store/mod.rs - Column family operations

🎉 Expected Outcomes

• Functional Command: RecycleCleanCommand will actually work instead of failing
• Consistent User Experience: Standardized logging and input handling
• Better Performance: O(1) deletion for full cleanup scenarios
• Maintained Safety: All existing safety features preserved
• Better Observability: Structured logging for debugging and monitoring

🏷 Labels

bug, enhancement, area::db, status::ready-for-dev

🔗 Related Is...