test_check_command_response - fix for 2.0.9 Jenkins

The code assignment is now identical even if it is duplicated/redundant, and the test fix seems better than more significant message reconstruction to mirror what DB#command does in Cursor#next.  The new driver should only do this in one place if possible, but for 1.x-stable, I think that this fix is appropriate/minimal.