update_engine: Replace NULL with nullptr

Replaced the usage of NULL with nullptr. This also makes it possible to
use standard gtest macros to compare pointers in Update Manager's unit tests.
So, there is no need in custom UMTEST_... macros which are replaced with the
gtest macros (see change in update_engine/update_manager/umtest_utils.h):

UMTEST_ASSERT_NULL(p)      => ASSERT_EQ(nullptr, p)
UMTEST_ASSERT_NOT_NULL(p)  => ASSERT_NE(nullptr, p)
UMTEST_EXPECT_NULL(p)      => EXPECT_EQ(nullptr, p)
UMTEST_EXPECT_NOT_NULL(p)  => EXPECT_NE(nullptr, p)

BUG=None
TEST=FEATURES=test emerge-link update_engine
     USE="clang asan" FEATURES=test emerge-link update_engine

Change-Id: I77a42a1e9ce992bb2f9f263db5cf75fe6110a4ec
Reviewed-on: https://chromium-review.googlesource.com/215136
Tested-by: Alex Vakulenko <avakulenko@chromium.org>
Reviewed-by: Alex Deymo <deymo@chromium.org>
Commit-Queue: Alex Vakulenko <avakulenko@chromium.org>
diff --git a/postinstall_runner_action.h b/postinstall_runner_action.h
index ee7c0b8..e7ac1c5 100644
--- a/postinstall_runner_action.h
+++ b/postinstall_runner_action.h
@@ -19,7 +19,7 @@
  public:
   PostinstallRunnerAction()
       : powerwash_marker_created_(false),
-        powerwash_marker_file_(NULL) {}
+        powerwash_marker_file_(nullptr) {}
 
   void PerformAction();
 
@@ -44,8 +44,8 @@
   // False otherwise. Used for cleaning up if post-install fails.
   bool powerwash_marker_created_;
 
-  // Non-NULL value will cause post-install to override the default marker file
-  // name; used for testing.
+  // Non-null value will cause post-install to override the default marker
+  // file name; used for testing.
   const char* powerwash_marker_file_;
 
   // Special ctor + friend declaration for testing purposes.