Fixed formatting for README from commit 214af367

Additional for CLT-319
Improve message when the jar file was auto updated
Updated td-client gem dependency to v0.8.62 and set ruby version to ~> 1.9.3
Rollup version
Revert ruby version requirement
Add hook to create pkg from local td-client gem
Fix spelling
v0.11.2

* Improve the update experience by showing a download progress indicator
* Fix issue on Windows OS where the JAR version file handle was not closed
  and caused permissions access problems to the file in subsequent attempts
  to open the file
* Add support for other/alternative backends using the -e / --endpoint
  option. The backend can be also saved on the configuration file of use
  via the 'td server:endpoint' or when running 'td -e <newendpoint> account'
  command. The TD_API_SERVER environment variable still takes precendence
  over all these settings
* Removed Treasure Data Result Output database and table name client side
  validation since it's performed in the API backend
* Suppress stack traces for APIError exceptions from the client library
* Changed the default HTTP port from 80 to 443 when interacting with the API
  server to support SSL
* Support working entirely without a configuration file (hence without
  having to run 'td account' prior to using the CLI) by passing the -k option
  on the command line
* don't wipe out the current JAR file if an attempt to retrieve the most updated
  JAR file failed because of network connectivity problems
* Show the job result only for finished jobs: unfinished jobs don't have any
  result to display anyway)
* Honor the HTTP_PROXY setting also when updating the JAR file or the Toolbelt
  itself
* Fix parsing of the HTTP_PROXY variable for the Bulk Loader's usage
* Allow optionally disabling the JAR file auto-update feature by setting the
  TD_TOOLBELT_JAR_UPDATE environment variable to 0
Support name update for schedules

Changes:
* add -n / --newname option to 'sched:update' command
* use alternative message if updating the schedule's name

Frontend for CLT-357
Update the Bulk Import JAR file repository

Changes:
* the Bulk import JAR file has been moved from
  Treasure Data own Maven repository to Maven
  Central for better server reliability in serving
  the update requests from the CLI
* Additionally, refactored around some File handling a bit

Implements CLT-362
Require Ruby 1.9 or superiod in the Gemspec

Attempt to fix CLT-224
Limit keys per record for JSON and MsgPack files

Changes:
* check each record parsed from JSON or MsgPack file and ensure
  that the number of keys does not exceed the hard limit of
  512 per record. Reject the record if it does
* added new exception class ImportError
* added handling of ImportError exceptions in runner.rb to
  suppress displaying stack traces
* moved the validation of the parsed input from JSON and Msgpack
  files to a generic base class StructuredParser to reduce
  code duplication between the two classes

Implements CLT-347
Handle NotFound, Forbidden, Auth errors

Changes:
* hide stack trace for known exceptions
* show stack trace when -v / --verbose option is used as well
Fix 'td import:create' with import-only permission

Changes:
* Remove client validation for db and table to avoid incurring
  in a failure because an API key that has import only permissions
  to a database cannot list tables. The validation on whether
  the table exists is deferred to the APIs (server side validation)

NOTE: creating a bulk import session with a write-only
      API key is currently not possible

First part of CLT-330
Allow 'table:import' with write-only dbs and keys

Changes:
* if getting a reference of the database fails for permissions
  (as in the write-only API key case) just print a warning that
  database/table validation is skipped and attempt to continue.
  The API will eventually forbid the import if not allowed
* if getting a reference of the database is successfull but getting
  a reference to the table fails for permission (as in the import
  only permission with the master API key case) just print a warning
  that table validation is skipped and attempt to continue.
  The API will eventually forbid the import if not allowed

Implements CLT-361
Fix out-of-scope variable from commit 4e5ec539
Show exception class for API errors
Propagate errots/status to 'td' entry point
Support idcfcloud.com domains

Changes:
* relax string based validation of the domain by limiting
  validation on the IP address alone
* verify the IP endpoint is valid by checking the status
  endpoint /v3/system/server_status
* NOTE: if the -e option is used, a call to the health
  check api will happen at every command...

Fixes CLT-396
Suppress testing the API endpoint from the command-line for select commands (e.g. import:prepare)

Changes:
* add a additional method and variable to the CommandOption class
* mark commands that don't require connectivity (API, toolbelt or
  JAR update indifferently) in the 'add_list' factories of list.rb
* separate validation and test for the API endpoint
* if the endpoint is provided as -e / --endpoint, test
  connectivity if the command requires it
* if the endpoint is setup with the server:endpoint command,
  test the connectivity immediately
* if the endpoint comes from the configuration file, connectivity
  has been checked before, the test is not repeated

Improves and fixes CLT-396