API: Split peer.py

[JurgenR]

Split peer.py functionality into modules:

• search.manager or just move it into search.py : everything related in peer.py related to searching
• distributed.py : everything related to distributed network

There's also other search related things that could move from other things to this new search manager:

• state.py : received_searches and search_requests fields
• server.py : the wishlist task could be moved to the new search module
• server.py : should query, query_room be moved to here as well?

Note: I have yet to understand if there might be an impact: peer.py currently also passes search requests on the children so the distributed.py needs to keep listening for search requests

[JurgenR]

What to do with generic peer requests (PeerUserInfoRequest etc?)

[JurgenR]

Debating whether the managers should be functionality focused instead of focused on the type of messages they receive

[JurgenR]

Splitted into a SearchManager and DistributedNetwork class. There's 3 messages that remain in PeerManager:

• PeerSharesRequest
• PeerDirectoryContentsRequest
• PeerUserInfoRequest