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 #318 from smarterclayton/bug_915255_track_user_preference_for_auth

Merged by openshift-bot
Merge pull request #319 from smarterclayton/bug_917514_require_one_argument_to_authorization

Merged by openshift-bot
Automatic commit of package [rhc] release [1.5.8-1].
Merge pull request #320 from smarterclayton/bug_917721_catch_exceptions_in_ssh_key_parse

Merged by openshift-bot