docs: fix setup instructions for Mailgun and S3

Summary: The S3 fields are mandatory and if you only enter the ones in the docs you will immediately encounter a "Amazon S3 is Only Partially Configured" error. For Mailgun the error is more difficult to figure out - emails get stuck on Mailgun's side but the error is illegible. On Phabricator's side you have to go trawling through nginx logs to find "Mail signature is not valid. Check your Mailgun API key."

Test Plan: Deploy a new standalone instance, follow old instructions, fail. Deploy another one, follow updated instructions, win.

Reviewers: epriestley, #blessed_reviewers

Reviewed By: epriestley, #blessed_reviewers

Subscribers: Korvin

Differential Revision: https://secure.phabricator.com/D15931

src/docs/user/configuration/configuring_file_storage.diviner

@@ -164,6 +164,8 @@ To enable file storage in S3, set these keys:
 
   - `amazon-s3.access-key`: Your AWS access key.
   - `amazon-s3.secret-key`: Your AWS secret key.
+  - `amazon-s3.region`: Your AWS S3 region.
+  - `amazon-s3.endpoint`: Your AWS S3 endpoint.
   - `storage.s3.bucket`: S3 bucket name where files should be stored.
 
 Testing Storage Engines

src/docs/user/configuration/configuring_inbound_email.diviner

@@ -128,6 +128,7 @@ like this:
   - Add a Mailgun route with a `catch_all()` rule which takes the action
     `forward("https://phabricator.example.com/mail/mailgun/")`. Replace the
     example domain with your actual domain.
+  - Set the `mailgun.api-key` config key to your Mailgun API key.
 
 = SendGrid Setup =