Update LWR client through LWR changeset 295fbb09de58.
Main addition here is introduction of logic for handling of implicit working directory files - namely those needed for variable count outputs (should work immediately) and setting metadata externally (requires additional changes).

Fixes bugs related to uploading empty working directory files (cannot mmap empty file) and incorrectly cleaning up of sucessful jobs when cleanup_job=never. As well as various readibility-centric refactorings.

Most interesting LWR commits this covers includes:

https://bitbucket.org/jmchilton/lwr/commits/1886ad1c0951605d2bc1a6e167f84f578563e470
https://bitbucket.org/jmchilton/lwr/commits/295fbb09de582a369e72d4331708be3f2f722e88
https://bitbucket.org/jmchilton/lwr/commits/45f0c818b91adfd63a9a4b3488a4a0d8bec1e991
Allow command_factory.build_command to pass in metadata kwds.
Add unit tests both for the old default parameters and the ability to replace these defaults.

This is all in case one wants to run the set metadata command on a remote server with different galaxy path, output paths, etc....
Eliminate non-specific exception catching in LWR runner.
This is a Python anti-pattern that should probably be eliminated throughout Galaxy.
Refactor queue_job in LWR job runner to more managable pieces.
Allow setting metadata remotely with the LWR.
Must be running against very new LWR server which has been configured with a GALAXY_HOME variable.

The LWR job runner is reorganized to fetch the remote job config earlier and the LWR passes more information during this setup phase (namely galaxy_home - that is used when building the metadata setting command).

There is a new destination parameter - use_remote_datatypes. This can be true or false - defaulting to false. When false - the local Galaxy integrated datatypes will be sent over to the remote LWR server and used in conjuction with the galaxy server configured remotely. When true - the remote LWR job manager should be configured with a 'galaxy_datatypes_config_file' parameters and this datatypes config file will be used when setting metadata externally.

Since both options are subtley broken because there is no guarentee the remote and local Galaxy instances have the same datatypes available - I guess I would personally recommend continuing to set metadata on the galaxy server in conjunction with the LWR.