chore: drop redundant block processing (#349)

Author: xdustinface

TEST_SUMMARY.md

@@ -47,7 +47,6 @@ I have successfully implemented comprehensive unit tests for several critical da
 - **Location**: 
   - `dash-spv/src/client/config_test.rs`
   - `dash-spv/src/client/watch_manager_test.rs`
-  - `dash-spv/src/client/block_processor_test.rs`
   - `dash-spv/src/client/consistency_test.rs`
   - `dash-spv/src/client/message_handler_test.rs`
 - **Issue**: Tests were written against an incorrect API and need adjustment

dash-spv/ARCHITECTURE.md

@@ -524,7 +524,6 @@ client/
 ├── events.rs (46 lines) - Event handling
 ├── queries.rs (173 lines) - Peer/masternode/balance queries
 ├── chainlock.rs (150 lines) - ChainLock processing
-├── block_processor.rs (649 lines) - Block processing
 ├── config.rs (484 lines) - Configuration
 ├── filter_sync.rs (171 lines) - Filter coordination
 ├── message_handler.rs (585 lines) - Message routing
@@ -557,31 +556,6 @@ client/
 
 **Refactoring needed**: ❌ None - this is exemplary
 
-#### `src/client/block_processor.rs` (649 lines) ⚠️ COMPLEX
-
-**Purpose**: Processes full blocks downloaded after filter matches.
-
-**What it does**:
-- Downloads full blocks for filter matches
-- Extracts relevant transactions
-- Updates wallet state
-- Emits transaction events
-
-**Complex Types Used**:
-- `mpsc::UnboundedSender<BlockProcessingTask>` - **JUSTIFIED**: Task queue pattern
-- Async task spawning - **JUSTIFIED**: Parallel block processing
-
-**Analysis**:
-- **GOOD**: Proper separation from main client
-- **GOOD**: Async task management
-- **ISSUE**: Could benefit from retry logic for failed downloads
-- **ISSUE**: No priority queue (all blocks treated equally)
-
-**Refactoring needed**:
-- ⚠️ **MEDIUM**: Add retry logic with exponential backoff
-- ⚠️ **MEDIUM**: Add priority queue (recent blocks first)
-- ✅ **LOW**: Add timeout configuration
-
 #### `src/client/filter_sync.rs` (289 lines) ✅ GOOD
 
 **Purpose**: Coordinates compact filter synchronization.