Make expect_that! more hygienic

related google#475

I went for using fully qualified method names, rather than `use $crate::GoogleTestSupport as _;` since it's more hygienic.

`use $crate::GoogleTestSupport as _;` can cause issues, resulting in a conflict, if the user introduces another method with the same name as one on `GoogleTestSupport`

googletest/src/assertions.rs

@@ -1359,14 +1359,16 @@ macro_rules! assert_pred {
 #[macro_export]
 macro_rules! expect_that {
  ($actual:expr, $expected:expr $(,)?) => {{
- use $crate::GoogleTestSupport as _;
- $crate::verify_that!($actual, $expected).and_log_failure();
+ $crate::GoogleTestSupport::and_log_failure($crate::verify_that!($actual, $expected));
  }};
 
  ($actual:expr, $expected:expr, $($format_args:expr),* $(,)?) => {
- $crate::verify_that!($actual, $expected)
- .with_failure_message(|| format!($($format_args),*))
- .and_log_failure()
+ $crate::GoogleTestSupport::and_log_failure(
+ $crate::GoogleTestSupport::with_failure_message(
+ $crate::verify_that!($actual, $expected),
+ || format!($($format_args),*)
+ )
+ )
  };
 }