Improve error handling when publish artifact fails due to insufficient disk space

The publication of artifacts can fail if there is insufficient disk space. Currently this produces no explicit error message, which makes it hard to track down such an error.

Steps to reproduce

1. Fill up the bamboo.home directory so there is little disk space left (this can be checked on the Bamboo "System information" page.
2. Run plan to upload a large artifact that exceeds the available disk space.

 Expected results

The plan fails with an error message like "Publish artifact failed due to insufficient disk space".

Actual results

Artifact publication fails with a nondescript error like the following:

error	20-Nov-2017 21:03:57	Unable to publish artifact [Zip files]: 
simple	20-Nov-2017 21:03:57	The artifact hasn't been successfully published after 42.10 s

Note: this was tested using a remote agent and "Bamboo remote handler" and "Server-local artifact handler" configured on the server.