Fixing spec test

Some versions of the JSON parser include a line number in the error message, causing the expected message to fail.

For https://tickets.puppetlabs.com/browse/RAZOR-135
Do not convert keys that look like ints into ints

Razor::CLI::Navigate.move_to was converting a key that looked like an
integer to an integer, solely based on whether that conversion could be
done or not. That is wrong for several reasons, most importantly because
the data type of what we compare the key against in the documents received
from the server does and should not depend on whether something can be
represented as an integer or not.

In the code that used the converted key, it was used to either find an
entry in an array of hashes where the 'name' property of the entry matches
the key, or to retrieve an entry from the (Hash) document we are working
on. In both cases, what we compare the key to must be a string; if it is
not a string, that's a violation of the API contract, and the client's
behavior just glossed over that.
Add client-side command help

This takes steps to provide help for each command to the user. It does this by doing a GET against the command's endpoint on the server then formatting the server's help JSON for output in the CLI.

This handles a wide variety of formats, including:
- `razor command --help`
- `razor command -h`
- `razor --help command`
- `razor -h command`
- `razor command help`
- `razor help command`
Fix create-repo CLI

The `task` attribute should be transformed into JSON when sending to the server.