OpenShift Wizard should prevent the user from cloning if he did not uplod a public ssh key to OpenShift yet

If the end-user's .ssh directory is empty - we should provide a stronger warning for them - ideally provide a URL to some documentation/video explaining how the user can use Eclipse/JBoss Tools to create their private/public keys - so they can then upload the .pub to OpenShift.

At least 10 users failed this test today and had to be "handheld" through the process.

What is worse, if the end-user uploads a slightly butchered pub key - the create application phase still works but the git clone fails - with a relatively poor error message - recovery normally means having to go up to the OpenShift console, deleting the poorly created apps - getting the pub key uploaded correctly (deleting the previous one) and starting again.

The fact that Eclipse could create the keys was actually unknown by the instructor's of today's class. SSH is still a nightmare for the newbie trying to use OpenShift + JBDS.

How to reproduce:

1. ASSERT: make sure you have an OpenShift user without a domain (create a new user or kill your users domain)
2. EXEC: launch OpenShift Application wizard and create a new application

Result:
Cloning fails, since there are no ssh-keys on the local machine and no keys were added to OpenShift. The wizard did not tell the user since the domain already existed. The domain creation dialog is currently the only place that would allow a user to create a new ssh-key. If you already have a domain, you'll never get asked to create your keys.