Sharing an `ApiDescription` with multiple server instances

If one wants to run the same set of endpoints in multiple servers (e.g., in the example added in #543), one awkward corner of dropshot's API is that ApiDescription is not cloneable, so it must be recreated from scratch for each server instance. A couple possibilities, neither of which is trivial to implement:

1. We could implement Clone for ApiDescription, but it can't be derived (and many of the types that would also need to implement Clone cannot either) because doing so would require the server context to be cloneable, but that isn't actually necessary to clone the description.
2. We could find a way to sprinkle in some Arcs to allow sharing an ApiDescription between multiple servers. It's not immediately obvious how to do this due to ApiDescription::into_router() consuming the ApiDescription.

Start by reading dropshot/src/api_description.rs, especially ApiDescription::into_router() and the surrounding ownership of server context. Trace how an ApiDescription becomes a router and determine what design would let multiple server instances share the endpoint description without recreating it; done means the same description can support multiple servers while preserving the existing context semantics.