Catch 404 response when wp cli `rm` command is used

currently if you try to run `wp s3-uploads rm` and pass in a path to an object that is not found, will return a success message, despite the object not being found. We should make it clearer when it's a 404 instead of a misleading success message.

Start by reproducing `wp s3-uploads rm` with a path for an object that does not exist, then trace the command's handling of the 404 response. Done means the command clearly reports the 404 instead of displaying a success message.

Written by the indexing model from the issue text.