Replace webkitpy standalone builders functions with instantiable class.

third_party/WebKit/Tools/Scripts/webkitpy/common/host.py

Index: third_party/WebKit/Tools/Scripts/webkitpy/common/host.py
diff --git a/third_party/WebKit/Tools/Scripts/webkitpy/common/host.py b/third_party/WebKit/Tools/Scripts/webkitpy/common/host.py
index 1f47fd762995a4b7d507fc5676c9f8e963e4c8d2..955405783f27100ee627ea5c65225a56cba1e4a6 100644
--- a/third_party/WebKit/Tools/Scripts/webkitpy/common/host.py
+++ b/third_party/WebKit/Tools/Scripts/webkitpy/common/host.py
@@ -35,6 +35,7 @@ from webkitpy.common.checkout.scm.detection import SCMDetector
 from webkitpy.common.memoized import memoized
 from webkitpy.common.net import buildbot, web
 from webkitpy.common.system.systemhost import SystemHost
+from webkitpy.layout_tests.port.builders import Builders
 from webkitpy.layout_tests.port.factory import PortFactory
 
 
@@ -60,6 +61,8 @@ class Host(SystemHost):
 
         self._engage_awesome_locale_hacks()
 
+        self.builders = Builders()

[qyearsley, 2016/05/02 21:56:36]

In general, does it make sense for builders to be a member attribute of Host?
(Does Host represent the specific machine that's running a command or tests?)

[bokan, 2016/05/04 11:58:47]

Host seems to be a general global state object. I'm not sure where else this
could be put so it would be accessible where needed. Port is the other obvious
candidate but we need the list of builders in order to construct a Port so that
can't be it. Dirk might know more if this is appropriate.

[Dirk Pranke, 2016/05/04 22:42:36]

Host is appropriate enough; we don't need to over-think this.

+
     # We call this from the Host constructor, as it's one of the
     # earliest calls made for all webkitpy-based programs.
     def _engage_awesome_locale_hacks(self):