Enhancement: probe vCenter to identify actual version

[zdeems]

Instead of attempting to deduce what path to use based on trial and error, probe vCenter to obtain the current version, then massage the path (if necessary) accordingly.  Set the 'default' behaviour to that of the most recent version to avoid having to constantly update to keep up with new vmware versions... then you only have to update when the newest version starts to behave differently.

[rwmjones]

I have absolutely no idea what you're talking about. Please answer the questions in the other bug.

[zdeems]

vCenter.ml currently runs checks based on historical behavior of vCenter in an effort to try and figure out how to handle the migration.  Issue 29 demonstrates breakage when attempting to migrate from vCenter 7.0.3 due to the path no longer matching the supplied regex (at least that's my read on the problem).  You only need the regex if you dont know the actual behaviour to expect from the other end.  If you start the process out by using the supplied credentials to probe vCenter for the vmware version, then you start to be able to program based on what you DO know rather than what you DON'T.  You already have access to the components you'd need to do it... the vcenter address, a userid and a password.