Add infrastructure applications to DuperModel

 DuperModel is (will be) responsible for both active tenant applications
(through SuperModel) and infrastructure applications. This PR is one step
in that direction:
 - All infrastructure applications (config, confighost, controller,
   controllerhost, and proxyhost) are owned and managed by DuperModel.
 - The InfrastructureProvisioner retrieves all possible infra apps from the
   DuperModel (through a reduced API), and "activates" each of them if
   target is set and there are any nodes etc.
 - The InfrastructureProvisioner then notifies the DuperModel which
   apps have been activated, and with which hosts.
 - The DuperModel can then build delegate artificially create ApplicationInfo,
   which gets translated into the application model, and finally the service
   model.
 - The resulting service model has NOT_CHECKED for each hostadmin service
   instance. This is sufficient for goal 1 of this sprint.
 - The config server application currently has health, so that's kept as-is
   for now.
 - Feature flags have been tried and works and allows 1. to disable adding the
   infra apps in the DuperModel, and 2. to enable the infra configserver
   instead of the currently created configserver w/health.

1 files changed, 6 insertions, 0 deletions

diff --git a/service-monitor/pom.xml b/service-monitor/pom.xml
index b8065ed3636..168af826b40 100644
--- a/service-monitor/pom.xml
+++ b/service-monitor/pom.xml
@@ -36,6 +36,12 @@
         </dependency>
         <dependency>
             <groupId>com.yahoo.vespa</groupId>
+            <artifactId>flags</artifactId>
+            <version>${project.version}</version>
+            <scope>provided</scope>
+        </dependency>
+        <dependency>
+            <groupId>com.yahoo.vespa</groupId>
             <artifactId>component</artifactId>
             <version>${project.version}</version>
             <scope>provided</scope>