The objectstore can not be embedded into the service factory because
the objectstore metadata services are inside the service factory. The
DAG of the dependencies prevent this, so to move forward, we can copy
what we've done with the provider tracker worker.

This introduces the concept for the workers. Adding it to the agent
manifolds and pushing it through the API is still required.

The objectstore dependencies have been changed to the objectstore
services (old terminology: object store service factory). This will
allow us to inject the objectstore into the service factory.

There is still a lot to fix, but according to the manifold tests,
we can clearly see that it's possible. So given that signal, I'm
going to press on and complete this.

The controller also has a object store, that also needs to be
migrated across to the new object store services.

The service factory (soon to be renamed) is becoming lighter and
is only offering the services that are serviable by the API
server.

The domain services are in fact real services, not infrastructure.

This is end game.

If this works, it means that we can access the blob store as a
dependency as a first class citizen. This has already shown real
value when it was done for the provider tracker.

The following wires up all the service factory dependencies correctly.
It's now possible to have the object store in the service factory.

There is a question around if the service factory should have a
deprendency on the upgrade database. Originally it didn't because
it's lazy evaluated. Now it's been introduced by the objectstore.

I wonder if that's going to cause us issues.

Now that objectstore has been dropped from the service factory, we
need to regenerate the mocks.

Model is much more discriptive than singular and it gives context
to the resulting expectation.