AWS settings for XBlocks to have filesystem-like storage

@cpennington @jarv PR to add s3fs support to aws.py. 

I tested this on sandbox to make sure edx-platform still works. I did not test whether configuring djpyfs works. I do not have a way to test this within the next 30 minutes. The Profile block requires backports from xblock-sdk to edx-platform. The pyfs-backed recommender has an issue working on sandbox, irrespective of this patch, and I'm still figuring out how to debug on sandbox. I won't have that done in the next 30 minutes. 

However, this is zero risk for now, since I'm not deploying anything which requires the above at the same time. Old recommender and everything else works fine. 

Mind if I merge prior to cut-to-release? If it works, it will save time later as we're debugging. If it doesn't work for any reason, little harm done (will need to be cleaned up in a new patch). 

Next step would be to add the matching tokens to the JSON config file. 
I renamed to fs-storage. I don't think that's a nit -- the naming here is important.

I'd prefer sandboxes to use S3 as well, actually. There are a lot of things which can go wrong changing storage back-ends, and sandboxes ought to reflect deployment environment there as much as possible. In an ideal case, we'd have a common bucket, but the prefix would reflect the specific sandbox. That's probably not v1.