Ban plaintext passwords

In version 0.7.0 we deprecated the use of plaintext passwords in FOG_RC
in a conscious move to promote that as bad practise. Interaction with
vcloud-tools should now be done by supplying a token, which can be
gained using `vcloud-login` (which will accept a password on STDIN).

This involved:

 - Moving check_plaintext_pass into Vcloud::Core::Fog
 - Calling check_plaintext_pass from check_credentials
 - replacing call to check_plaintext_pass from Vcloud::Core::Fog::Login
   with call to Vcloud::Core::Fog.check_credentials
 - Rescuing call to Vcloud::Core::Fog.check_credentials in
   `vcloud/core/fog.rb` to provide a nice error message to the user

Happy to be guided on better ways to do this - it's my first solo foray
into vcloud-tools.

Rubocop and Specs pass. Not much changed in the test apart from the
expected error message, which I have lengthened slighly to describe the
reason behind the error as well as what it means.
A newline separating `end` and `begin` would make this more readable.

I'm not sure that this is the right place to catch this error; `vcloud-core` is intended to be used as a library so I don't think we should make assumptions about outputting errors to `stderr`. Rather I think it should be up to the gem that uses this library to catch that; we could make the exception more specific (i.e. not `RuntimeError`) to make this easier to catch.