Update td-client gem dependency to v0.8.63
Rollup version
Improve result output download messages

Improves CLT-202
Improve result output tabular format download

Improves CLT-202
Fix call to static jarfile_dest_path helper

Fix commit ea6a37e
Add envvar hook to customize the JAR update endpoint for test
v0.11.3

* Support name updates for schedules using sched:update command
* Update Bulk Import JAR file repository to Central Maven Repository where
  the Bulk Import JAR file is now hosted
* Require Ruby v1.9 or superior for td to work ==> deprecated Ruby v1.8
* Limit the number of keys in the input file (JSON, Msgoack) that can be
  imported in one import to 512 as per the backend's limitations
* Fixed import:create to work with import-only permissions and write-only API
  keys
* Handle NotFoundError, AuthError, and ForbiddenError to suppress printing of
  the exception stack traces but yet show the exception class name for reference
  back to the actual HTTP error code
* validate the endpoints provided by -e / --endpoint using the Health-check
  REST API /v3/system/server_status. Validation is avoided for any command
  that does not require connectivity with the Treasure Data REST API server
* JAR update errors are ignored when running import:prepare. This command
  does not require connectivity and can be ran even when the machine is not
  connected to the internet
* Fixed Time based progress indicator to reflect the update interval exactly
* Read logging.properties Logging configuration file from ~/.td/java first,
  then the td repository's location (default). This allows customization of
  the logging for the Java Bulk Import CLI (td-import-java).
* Improve job result downloading by showing the total downloaded size and
  percentage progress (Size based progress indicator). This is done when
  printing the result in tabular format or writing the result on file in csv,
  tsv, json, msgpack, or msgpack.gz formats. When displaying the result in csv,
  tsv, and json format on stdout, the progress indicator is not used since the
  data is progressively streamed in as it's received from the API server