Don't require s3:// prefix on ls commands

The path will always refer to an s3 object,
so it's not necessary to specify s3://.  Now
we support both versions:

* aws s3 ls s3://bucket-name
* aws s3 ls bucket-name