[pre-provisioned][doc] Clarify deployed-server network choices for tripleo/quickstart docs

[Bogdan Dobrelya]

It is not clear what ::Net::SoftwareConfig templates are optimal for pre-provisioned overcloud nodes running on openstack cloud. Those need to be documented as example deploy commands for fast-and-easy dev envs, w/o network isolation perhaps.

There are several points to be clarifed in either t-h-t or oooq docs, or both:
* The t-h-t default environments, like http://codesearch.openstack.org/?q=docker-network.yaml&i=nope&files=&repos=, seem overlapping to the oooq-extras resource_registry_args vs resource_registry_nic_configs_args vs deployed-server networking config logic.
So '-e <tht-path>/docker-network.yaml' need to be omitted, if the resource_registry_args used, it seems.

* There are too many poorly documented choices for multinode/pre-provisioned/deployed-server, non-isolated-networks, setups:

- net-config-multinode.yaml http://codesearch.openstack.org/?q=net-config-multinode.yaml&i=nope&files=&repos= (CI exclusive use cases?)

- net-config-multinode-os-net-config.yaml (contains openstack CI noodepool exclusive bits).

- net-config-static-bridge.yaml(see also docs https://docs.openstack.org/tripleo-docs/latest/advanced_deployment/deployed_server.html and https://git.openstack.org/cgit/openstack/tripleo-heat-templates/tree/deployed-server/README.rst#n53 )

- net-config-bridge.yaml (t-h-t docs default choice documented for developers, see http://git.openstack.org/cgit/openstack/tripleo-heat-templates/tree/docker/README-containers.md)

Unclear use cases for the last two bring the most of the confusion, IMHO. Although, CI specific cases would be nice to documented as well.

[Bogdan Dobrelya (bogdando)]

Actually, I'm not sure what is the expected result for this.