wayland_buffer_fuzzer: fix Direct-leak in mojo::core::InitializeCore

This happens because mojo::core::Init() is being called multiple times.

Move that into the Environment setup.

Bug: 1124902
Change-Id: I98a05ff1c813c32ae8f3223907c8cf22b2f078ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424164
Auto-Submit: Maksim Sisov (GMT+3) <msisov@igalia.com>
Commit-Queue: Nick Yamane <nickdiego@igalia.com>
Reviewed-by: Nick Yamane <nickdiego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#809304}

ui/ozone/platform/wayland/fuzzer/wayland_buffer_fuzzer.cc

@@ -65,6 +65,8 @@ struct Environment {
                           TestTimeouts::Initialize(),
                           base::test::TaskEnvironment::MainThreadType::UI)) {
     logging::SetMinLogLevel(logging::LOG_FATAL);
+
+    mojo::core::Init();
   }
 
   base::test::TaskEnvironment task_environment;
@@ -76,7 +78,6 @@ extern "C" int LLVMFuzzerTestOneInput(const uint8_t* data, size_t size) {
   static Environment env;
   FuzzedDataProvider data_provider(data, size);
 
-  mojo::core::Init();
   base::CommandLine::Init(0, nullptr);
 
   std::vector<uint32_t> known_fourccs{