ImplementsServer verifies that a given `*mux.Router` has handlers for all routes specified in `NewAPIRouter()`.

These (routes, and constructor following) should move to weaveworks/flux-adapter when `--connect` is removed from fluxd.

This is part of the API -- but it's the outward-facing (or service provider) API, rather than the flux API.

Formerly Upstream methods, now (in v11) included in server API.

The RegisterDaemonX routes should move to weaveworks/flux-adapter once we remove `--connect`, since they are pertinent only to making an RPC relay connection.

The RegisterDaemonX routes should move to weaveworks/flux-adapter once we remove `--connect`, since they are pertinent only to making an RPC relay connection.

The RegisterDaemonX routes should move to weaveworks/flux-adapter once we remove `--connect`, since they are pertinent only to making an RPC relay connection.

The RegisterDaemonX routes should move to weaveworks/flux-adapter once we remove `--connect`, since they are pertinent only to making an RPC relay connection.

The RegisterDaemonX routes should move to weaveworks/flux-adapter once we remove `--connect`, since they are pertinent only to making an RPC relay connection.

The RegisterDaemonX routes should move to weaveworks/flux-adapter once we remove `--connect`, since they are pertinent only to making an RPC relay connection.