parse can parse connections

@imlucas 

as per the spec, when parsing connections, there are two cases to consider 
1 - the thread name is of format 'conn#', then the connection is the same value of the thread name e.g.
- "2014-05-31T14:21:14.734-0400 [conn14] command admin.$cmd command: isMaster { ismaster: 1 } keyUpdates:0 numYields:0  reslen:371 0ms"

2 - the log message is of format "connection accepted from {{IP_address}}:{{portNumber}} #{{connNum}}", the connection name is then 'conn' + {{connNum}} e.g.
- "2014-05-31T14:21:14.734-0400 [initandlisten] connection accepted from 127.0.0.1:51786 #14 (3 connections now open)"
// the connection is "conn14"

test.js -> parse.js
Instead of doing a assert.deepEqual, I changed it to be a assert.equal on each of the attributes since parse is now also parsing the new "conn" field which broke the test cases since the expected variable for each of those test cases does not have a "conn" field.