* lib/razor/cli/navigate.yaml: rename update-tag to update-tag-rule

The command was renamed, and the declaration needs to be renamed to match that
Print minimal help text if we can't connect to the server

If the client could not connect to the server for whatever reason, we used
to spew an uninformative backtrace. Now, we print a more helpful message.
Print a helpful message on SocketError

When running something like 'razor nodes', we used to just spew a
backtrace. Print a slightly more friendly error message.
Allow setting the connection URL with the RAZOR_API environment variable

This should make usage from the command line against a server that is not
local more convenient.
* spec/spec_helper.rb: clear RAZOR_API from environment before each test

This is needed to isolate the tests from whatever is set in the environment
in which tests are run.
Fail with useful error message if URL from -U or RAOR_API is invalid
Version 0.11.0

Updated the gemspec and fixed the author in it.
* README.md: point at the Getting Started guide in the razor-server Wiki
Do not JSON-decode tag rules twice

The Navigate::extract_command method calls JSON::parse twice when passed
the create-tag command's "rule" argument value, which triggers an exception
and crashes the client. The second call is unnecessary, so this patch
removes it.
* README.md: add pointer to JIRA bug tracker
* razor-client.gemspec: require at least Ruby 1.9.3
* bin/razor: set exit code on error; print nice error for invalid URL

  * Explicitly exit with error code 1 if there are any errors
  * Do not print a backtrace when API URL is invalid
Do not trip over empty hashes in responses

When objects contained an empty hash, for example a broker of type 'puppet'
with no additional configuration, Razor::CLI::Format::format_Default_object
would attempt to calculate [].max which fails miserably.

Now, we shortcircuit that and print empty hashes as '{}'

Similar to https://github.com/puppetlabs/razor-client/pull/9 submitted by
https://github.com/derekmwright
Remove the wrapper around collections

The API now returns an object for collections, instead of an array. The
actual collection elements are in the object's 'items' property. For now,
the client internally pretends that we still only get the items array back
from the server.

Corresponds to razor-server commit cf6c58e4
Convert literal string 'null' to nil

This is necessary so that users can pass a null for the max-count with
modify-policy-max-count
Version 0.12.0
Make razor-client work on Ruby 1.8.7 and 1.9
Version 0.12.1
Change the specification for the short --url option to lower case

It seems there is an interesting bug in optparse in that if the short spec
is upper case, it accepts both upper and lower case. Since there's no real
need to demand an upper case -U, we'll just go to lower case.

Fixes https://tickets.puppetlabs.com/browse/RAZOR-84
Version 0.13.0