Refactoring: cleanup, renaming and restructuring

[evlekht]

A lot of renaming, considerable amount of restructuring in messaging processor and responseHandler. Some cleanup.
Its quite hard to list every change, because its touching a lot of different places, but follows same general idea: make code more readable, more manageable.

[havan]

Tip

Adding AI generated summary and description of the changes to help with the review.

Message Processing Refactoring and Code Improvements

Overview

This PR introduces significant improvements to the messaging system implementation, focusing on better code organization, thread safety, and maintainability.

Key Changes

Message Processor

• Renamed Processor interface to MessageProcessor for better clarity
• Renamed implementation from processor to messageProcessor
• Added CompressedContent field to Message type to better handle message content compression
• Improved thread safety with RWMutex and encapsulated locking operations
• Split message processing into more focused functions:
• ProcessIncomingMessage (renamed from ProcessInbound)
• SendRequestMessage (renamed from ProcessOutbound)

Response Handler

• Refactored response handling logic into smaller, more maintainable functions
• Split mint response handling into separate prepare/process stages
• Added explicit error variable errMissingMintTxID
• Improved error handling patterns throughout
• Streamlined response processing flow

RPC Interface

• Renamed ExternalRequestProcessor to RequestHandler for better clarity
• Simplified interface methods
• Updated all generated code to align with new interfaces

Matrix Messenger

• Modified SendAsync signature to use pointer Message and remove separate content parameter
• Added check to ignore own messages in matrix messenger
• Improved message chunking and compression handling

Breaking Changes

• SendAsync method signature changed from (msg types.Message, content [][]byte) to (msg *types.Message)
• Interface renames may require updates to any external implementations
• Response handler interface changes require implementation updates

Testing

All existing tests have been updated to accommodate these changes. Test coverage remains comprehensive.

Future Work

While this PR significantly improves the codebase, some potential future improvements could include:

• Additional documentation for new patterns
• More comprehensive integration tests
• Performance benchmarking of new implementations

[havan]

Looks good to me.