structure output of nomad server members -detailed

`nomad server members -detailed` tag output is unstructured and unordered

```
→ nomad server members -detailed
Name Address Port Tags
server1.global 192.168.1.54 4648 build=0.11.0-dev+modules,rpc_addr=192.168.1.54,mvn=1,vsn=1,expect=2,raft_vsn=2,dc=dc1,id=5ee615db-3db2-d2d0-2bfd-81f5770ea87a,role=nomad,region=global,port=4647
server2.global 192.168.1.54 5648 role=nomad,mvn=1,port=5647,expect=1,raft_vsn=2,rpc_addr=192.168.1.54,dc=dc1,region=global,vsn=1,build=0.11.0-dev+modules,id=c3d8ceda-2c32-7544-850a-d53245071c5f,bootstrap=1
server3.global 192.168.1.54 6648 mvn=1,expect=2,role=nomad,dc=dc1,rpc_addr=192.168.1.54,vsn=1,port=6647,region=global,build=0.11.0-dev+modules,raft_vsn=2,id=a712035d-7b52-b25d-9241-1271291a064e
```

Issue is a placeholder to structure output better and potentially rename -detailed flag to -verbose

- specify which port `port` refers to (rpc/serf/http), add other ports

Start by running `nomad server members -detailed` and inspect the current CLI implementation for the server-members output. Clarify the desired structured and ordered fields, including which ports `port` represents and whether other ports should be shown; done means the output is consistently organized and the flag naming decision is resolved.

Written by the indexing model from the issue text.