ExpectServicesFromConn returns false for reconciliation connections

This description is AI generated, mistakes can be made.

Intent: Skip the desirable-service-flags check on VERSION for recon peers, so recon slots can be filled by pruned or non-witness peers that cannot serve blocks.

Behaviour change: Original: a recon outbound peer advertising services without NODE_NETWORK|NODE_WITNESS (e.g. NODE_NETWORK_LIMITED only while we are in IBD, or no NODE_WITNESS) is disconnected in ProcessMessage VERSION. Mutant: it is kept.

Trigger: Node with -txreconciliation opens an OUTBOUND_FULL_RECONCILIATION connection to a peer whose VERSION nServices lacks NODE_WITNESS (or is NODE_NETWORK_LIMITED during IBD); net_processing.cpp:3933 does not disconnect.

Spec violation: Commit: reconciliation connections 'relay everything a full-relay connection does (tx, block, addr)... Treat them as full outbound connections.'

Severity if undetected: medium

Why tests miss it: rg ExpectServicesFromConn src/test test/functional; p2p_txrecon_* / p2p_sendtxrcncl.py use default P2PInterface services (NODE_NETWORK|NODE_WITNESS); p2p_handshake.py tests service-flag disconnect only for full-relay/block-relay types

Plausibility: Recon connections are 'tx-only extras' in the PR narrative, so grouping them with FEELER as not needing services looks reasonable; one-line case move.

Equivalence risk: Peers lacking the flags are rare among addrman picks since addrman selection prefers desirable services, but ThreadOpenConnections can still pick them, so not equivalent.