automatically deploy git hooks upon clone

this permit to have a more productive default ( for example, checking
package.json format on commit for nodejs cartridge ) and allow
a team of developper to share a set of commit hooks by default, to
enforce compliance in a easier way.
add rspec test, but not working for now

Debugging seems to show this would be a issue in FakeFS
since it doesn't create the correct file for FileUtils.cp
Bug 916058 - Show error when auth token operation not supported
Merge pull request #312 from smarterclayton/bug_916058_inform_unsupported_auth_tokens

Bug 916058 - Show error when auth token operation not supported
Automatic commit of package [rhc] release [1.5.6-1].
rhc_extended: Fixed find_application in rhc_helper

This was causing the extended tests to fail after we moved
find_application from `domain` to `client`.
Bug 916122: Avoid misleading port-forwarding specification for MySQL.

mysql client forces UNIX socket if the host is specified as 'localhost'.
Avoid this by displaying the numeric IP.
Merge pull request #314 from fotioslindiakos/rhc_extended_fix

rhc_extended: Fixed find_application in rhc_helper
Merge pull request #315 from BanzaiMan/dev/hasari/bz916122

Merged by openshift-bot
During output, defend against exceptions caused by bad apps
Merge pull request #316 from smarterclayton/defend_against_exceptions_during_display

Merged by openshift-bot
Automatic commit of package [rhc] release [1.5.7-1].
Update reference to rubygems.org to avoid warning
Bug 915255 - Track auth preference in the config

During 'rhc setup', the user's choice to create an auth token is relevant to later interactions.  If a user declines tokens then later interactions should not recreate a token on disk, only prompt the user to login with their password.  This commit adds 'use_authorization_tokens' to the config and is a remembered value based on 3 states:

  1) did the user pass --no-create-token to the setup command?
  2) did a token get generated when the user hit 'yes'
  3) did the user pass a token to setup via --token?

The value is stored and remembered for future reference when a token expires
Bug 917514 - 'authorization delete' should require at least one token
Bug 917721 - Don't let exceptions get raised from fingerprint tests

Any fingerprint failures should be treated as a missing key (Errno::ENOENT, Errno::EACCESS)
Merge pull request #317 from BanzaiMan/gemfile_fix

Merged by openshift-bot
Merge pull request #318 from smarterclayton/bug_915255_track_user_preference_for_auth

Merged by openshift-bot
httpclient is too lazy for auth, sending double the number of necessary requests
Merge pull request #319 from smarterclayton/bug_917514_require_one_argument_to_authorization

Merged by openshift-bot