Skip tests that make no sense for the new write api
See PHP-981
The error ok field in the error document doesn't mean the same thing in 2.6

also remove useless mongolog entries that are not vailable in the new impl
Fix tests

- Remove the MongoLog that adds no value
- The old ipmlementation silently overwrite 'safe' with 'w'
- Bump w= to actually trigger an error
We no longer call gle.. so ignore it if its in the log
Fix test

'safe' was silently overwritten with 'w'.
The query/command logging also hits different triggers now, since writes are commands..
Different timeout error message in 2.5
This error message changed again inn 2.5
We actually need this to be float for bc
Make WriteConcern option checking case*in*sensitive, see PHP-810
Update exception throwing after the error type split in 2.5
Only read from the property if it hasn't changed and we didn't get anything else passed
Downvert 2.6 style return values to 2.4 style :(
Deregister the connection on all write errors

We can't 100% accurately differenciate parse errors to auth errors
or any other must-disconnect errors, so we do that on any write error
Return a boolean value on w=0, even though we treat it as w=1
Throw exception when the server doesn't support write commands or opcodes
Fix w=0 to not throw exception on failure
Fix BC with 2.4 servers
Duplicate these tests for 2.6
Don't overwrite write concern when w>safe