Signed-off-by: Dani Louca [email protected]

The changes in 34302 ignores the network details already collected in the previous backend block and causes docker network inspect -v <overlay_partial_ID to miss the "extra details" provided by the verbose flag.
The same issue exists with the network inspect API when querying a network overlay name and swarm scope, ex: curl --unix-socket /var/run/docker.sock "http:/v1.30/networks/<overlay_name>?verbose=true&scope=swarm"

Steps To Reproduce:

• create an overlay network and a service that uses it.
  docker network create -d overlay apps
docker service create --mode global --name runev --network apps alpine watch date
• get the network partial ID
  docker network ls -f driver=overlay -f name=apps -q
• inspect the network using using the partial ID
  docker network inspect -v 6yiu2vo3obja

Expected Results:
return all the extra info provided by the verbose flag, including endpoints, services etc...

Actual Results:
verbose information is missing

Same behavior applies to:
curl --unix-socket /var/run/docker.sock "http:/v1.30/networks/apps?verbose=true&scope=swarm"

Fix:
The fix does not alter the behavior added in 34302, it checks if the networkID returned by n.cluster.GetNetwork(term) has an entry in listByPartialID or listByFullName and returns it, otherwise it returns the basic network detail.