rename addons.js to services.js

services is the named container (services view)
addons is more like a heroku concept

src/platform.js

@@ -1,15 +1,14 @@
 'use strict';
 
 exports = module.exports = {
-    start: start,
-    stopAllTasks: stopAllTasks,
+    start,
+    stopAllTasks,
 
     // exported for testing
     _isReady: false
 };
 
-var addons = require('./addons.js'),
-    apps = require('./apps.js'),
+const apps = require('./apps.js'),
     assert = require('assert'),
     async = require('async'),
     debug = require('debug')('box:platform'),
@@ -20,6 +19,7 @@ var addons = require('./addons.js'),
     paths = require('./paths.js'),
     reverseProxy = require('./reverseproxy.js'),
     safe = require('safetydance'),
+    services = require('./services.js'),
     settings = require('./settings.js'),
     sftp = require('./sftp.js'),
     shell = require('./shell.js'),
@@ -58,7 +58,7 @@ function start(callback) {
         markApps.bind(null, existingInfra), // mark app state before we start addons. this gives the db import logic a chance to mark an app as errored
         graphs.startGraphite.bind(null, existingInfra),
         sftp.startSftp.bind(null, existingInfra),
-        addons.startServices.bind(null, existingInfra),
+        services.startServices.bind(null, existingInfra),
         fs.writeFile.bind(fs, paths.INFRA_VERSION_FILE, JSON.stringify(infra, null, 4))
     ], function (error) {
         if (error) return callback(error);
@@ -93,7 +93,7 @@ function applyPlatformConfig(callback) {
     settings.getPlatformConfig(function (error, platformConfig) {
         if (error) return callback(error);
 
-        addons.updateServiceConfig(platformConfig, callback);
+        services.updateServiceConfig(platformConfig, callback);
     });
 }