Fixes the test gmock_output_test.py with MSVC in a better way

[lygstate]

cc @thughes
After this mr:
the std::pair<> can be used directly

And the hacky for

#ifdef _MSC_VER
#define ERROR_DESC "class std::runtime_error"
#else
#define ERROR_DESC "std::runtime_error"
#endif

are no more needed

we can using

std::runtime_error

directly

[asoffer]

Can you describe what the issue is and why this fix is better (and what it's better than?)

[lygstate]

Can you describe what the issue is and why this fix is better (and what it's better than?)

updated the reason

[lygstate]

@thughes @asoffer ping

[asoffer]

Sorry, I'm still not sure I understand what the problem is here. Could you answer:

• What does gmock_output_test.py do on MSVC?
• What do you expect it to do?
• Why is this solution to that problem better than the existing solution?

[lygstate]

Sorry, I'm still not sure I understand what the problem is here. Could you answer:

• What does gmock_output_test.py do on MSVC?

For MSVC, gmock_output_test.py output struct std::pair<int,bool>, for GCC, it's output
std::pair<int, bool>, it's not the same, my intention is getting these to be same by removing
struct for MSVC's outptu, and strip redundant space for GCC.

• What do you expect it to do?

ditto.

• Why is this solution to that problem better than the existing solution?

The new solution can use std::pair<int,bool> directly, the exiting solution is avoid to use it,
this solution would be more robust that output consistence typename.
As a by-product,

#ifdef _MSC_VER
#define ERROR_DESC "class std::runtime_error"
#else
#define ERROR_DESC "std::runtime_error"
#endif

can be simplified to

#define ERROR_DESC "std::runtime_error"

cc @asoffer

[asoffer]

Just a few nits, but otherwise looks great. Thank you!

[lygstate]

@asoffer updated, can this be merged now?

[lygstate]

@derekmauro @asoffer ping?

[asoffer]

Apologies for the delay. Pulling this in.