Reflection: swift-reflection-dump now only needs a TypeRefBuilder and not a ReflectionContext, NFC

Since swift-reflection-dump does not have a remote address space,
it doesn't need a full ReflectionContext. Now that TypeRefBuilder
has been refactored, we can use that instead.

Author: slavapestov

tools/swift-reflection-dump/swift-reflection-dump.cpp

@@ -16,9 +16,8 @@
 #include "swift/ABI/MetadataValues.h"
 #include "swift/Basic/Demangle.h"
 #include "swift/Basic/LLVMInitialize.h"
-#include "swift/Reflection/ReflectionContext.h"
-#include "swift/Remote/InProcessMemoryReader.h"
 #include "swift/Reflection/TypeRef.h"
+#include "swift/Reflection/TypeRefBuilder.h"
 #include "llvm/Object/Archive.h"
 #include "llvm/Object/MachO.h"
 #include "llvm/Object/MachOUniversal.h"
@@ -204,10 +203,9 @@ static int doDumpReflectionSections(std::string binaryFilename,
     reinterpret_cast<const void *>(reflectionStringsSectionContents.end())
   };
 
-  // Construct the reflection context
-  auto reader = std::make_shared<InProcessMemoryReader>();
-  ReflectionContext<External<RuntimeTarget<8>>> RC(reader);
-  RC.addReflectionInfo({
+  // Construct the TypeRefBuilder
+  TypeRefBuilder builder;
+  builder.addReflectionInfo({
     binaryFilename,
     fieldSection,
     associatedTypeSection,
@@ -217,7 +215,7 @@ static int doDumpReflectionSections(std::string binaryFilename,
   });
 
   // Dump everything
-  RC.dumpAllSections(std::cout);
+  builder.dumpAllSections(std::cout);
 
   return EXIT_SUCCESS;
 }