Avoid unnecessary errors from ipa-replica-manage connect.

Since the topology can be known algorithmically before the puppet-ssh
module has had a chance to transfer the replica-info-*.gpg file, then
the ipa-replica-manage connect command can try and connect a peer before
the peer has even had a chance to ipa-replica-install first. This check
ensures that there is an ipa server up and listening first so that we
don't show unnecessary errors.

Of particular note is that I believe that I am somewhat mis-using the
ipa-replica-conncheck command to do this verification. It is actually
being used (AFAICT) to do exactly what it was designed to do, but I am
using it in an undocumented way, because I am expecting it to work
against a real ipa replica, instead of the fake listener that you would
run on your peer server with the ipa-replica-conncheck tool.

This error actually showed up in a strange way on 3.0.0, see:
https://fedorahosted.org/freeipa/ticket/3105

It should show up more intelligibly in 3.0.1, although it should
probably never be seen with this patch (unless there is a real problem).
Avoid a transient duplicate defn. during algorithmic topology shifts.

See the corresponding commit in the puppet-ssh source for more
information. Hopefully this fixes the issue permanently, even though it
was transient and "Mostly Harmless".
Initial structure of yamldata multi-os params.pp support.

This branch will be rebased as it is worked on...

TODO:

* Remove/Fix XXX parts.
* Add puppet-module-data module to vagrant submodules.
* Add other aspects of params.pp
* Add support for other OS's. (Remove XXX where present.)