ServerBuilder and listening

Currently, the standard way to listen on a socket is to call `addPort()`, but from recent requests, this API is too limited. I would like to explore some ideas for expanding this functionality. Specifically:

1. Make a standard way to add multiple ports to a single server.
2. Make it possible to listen on things other than ports, in particular `SocketAddress`es.
3. Make it possible to add more ports / sockets after a Server has been built.
1. This would effectively allow a server to add ports after `start()`
2. Maybe allow servers to gracefully close ports they started on.
3. Support having no listening ports on the builder. This would mean adding a ServerBuilder ctor that has no ports at all.

This issue is more exploratory rather than mandatory. Right now the request is just to listen on multiple ports, but we should be careful to not add overlapping APIs (such as on both Server and ServerBuilder).

cc: @ejona86

まず ServerBuilder と既存の addPort() のフローを読み、次に Server と start() がリスニングをどのように処理しているかを確認します。要求されている複数ポート、SocketAddresses、起動後の追加、正常なクローズを比較し、重複する API の選択肢を特定します。完了とするには、実装を定義できるようになる前に、スコープと設計について合意する必要があります。

索引モデルが issue の本文から書いたものです。