Query and Execute HTTP commands different behavior with edges

[lvca]

This issue was reported by biker70599 on the Discord channel.

Experimenting with the DB. If I fire a "command/{query} sequence to the http/json API, no edges are included in the result-set. They are returned if query/{query} is used.

3.1.1 :005 > DB.query "select  both()  from #1:0"    # fires query/ 
17.04.(12:59:58) INFO->Q: select  both()  from #1:0
 =>                                             
[{:"both()"=>                                   
   [{:@out=>10, :item=>10, :@rid=>"#28:1", :@in=>1, :@type=>"node", :@cat=>"v"},
    {:@out=>10, :item=>8, :@rid=>"#46:0", :@in=>1, :@type=>"node", :@cat=>"v"},
    {:@out=>10, :item=>9, :@rid=>"#25:1", :@in=>1, :@type=>"node", :@cat=>"v"}]}] 
3.1.1 :006 > 
3.1.1 :007 > DB.execute{ "select  both()  from #1:0" }  # fires command/
17.04.(13:00:12) INFO->Q: select  both()  from #1:0
 => 
[{:"both()"=>
   [{:item=>10, :@rid=>"#28:1", :@type=>"node"},
    {:item=>8, :@rid=>"#46:0", :@type=>"node"},
    {:item=>9, :@rid=>"#25:1", :@type=>"node"}]}] 

[lvca]

Now both HTTP commands share the same code for returning the resultset. Also, query now supports the optional parameters limit and serialzier.