RESOLVE control port command code path is incorrect
The codepath taken by the control port "RESOLVE" command to create a synthetic SOCKS resolve request isn't the same as the path taken by a real SOCKS request from 'tor-resolve'.
This prevents controllers who set __LeaveStreamsUnattached=1 from being able to attach RESOLVE streams to circuits of their choosing.