Incorrect error message when unable to create FS

[tasleson]

If you exhaust the pool when trying to create a FS you get:

# bin/stratis filesystem create raided fs3
Execution failure caused by:
INTERNAL ERROR: Command failed: cmd: "/usr/sbin/mkfs.xfs" "-f" "-q" "/dev/dm-17" "-m" "uuid=cc37f37d-3aa5-4d6d-8aeb-4f79af486eec", stdout:  stderr: mkfs.xfs: libxfs_device_zero write failed: No space left on device

Listing this as an INTERNAL ERROR seems incorrect considering that we ran out of space.

[mulkieran]

All errors in StratisError::Error are translated to an INTERNAL_ERROR before being place on the D-Bus. Most likely this is wrong in most instances where StratisError::Error occurs. All errors in StratisError::Uuid, StratisError::Utf8, StratisError::Serde, StratisError::DM, StratisError::Dbus, and StratisError::Udev are also being mapped to INTERNAL_ERROR. Ditto.

AFAIAC, our error handling in the D-Bus layer needs a complete overhaul.

[agrover]

duplicate of #1181 and #534, closing.