fusefs: revert a workaround for a googletest bug

This bug was fixed by googletest back in 2019 and released in googletest
1.10.0, I think.  Using GTEST_SKIP from a test environment works now.

https://github.com/google/googletest/issues/2189

MFC after:	2 weeks
Sponsored by:	ConnectWise

tests/sys/fs/fusefs/utils.cc

@@ -124,6 +124,7 @@ bool is_unsafe_aio_enabled(void) {
 
 class FuseEnv: public Environment {
 	virtual void SetUp() {
+		check_environment();
 	}
 };
 
@@ -132,14 +133,6 @@ void FuseTest::SetUp() {
 	const char *maxphys_node = "kern.maxphys";
 	size_t size;
 
-	/*
-	 * XXX check_environment should be called from FuseEnv::SetUp, but
-	 * can't due to https://github.com/google/googletest/issues/2189
-	 */
-	check_environment();
-	if (IsSkipped())
-		return;
-
 	size = sizeof(m_maxbcachebuf);
 	ASSERT_EQ(0, sysctlbyname(maxbcachebuf_node, &m_maxbcachebuf, &size,
 		NULL, 0)) << strerror(errno);