feat(s3): add CORS Property to S3 Bucket (#2101)

[workeitel]

Add CORS Property to S3 Bucket for configuring bucket cross-origin
access rules.

You can either specify the metrics as properties:

 new Bucket(stack, 'Bucket', {
   cors: [
     {
       allowedHeaders: [
         "*"
       ],
       allowedMethods: [
         "GET"
       ],
       allowedOrigins: [
         "*"
       ],
       exposedHeaders: [
         "Date"
       ],
       id: "myCORSRuleId1",
       maxAge: 3600
     }
   ]
 });

Or use the addCors function:

const bucket = new Bucket(stack, 'Bucket');
bucket.addCors({
  allowedMethods: ["GET", "HEAD"],
  allowedOrigins: ["https://example.com"]
});

---

Pull Request Checklist

• Testing
  • Unit test added (prefer not to modify an existing test, otherwise, it's probably a breaking change)
  • CLI change?: coordinate update of integration tests with team
  • cdk-init template change?: coordinated update of integration tests with team
• Docs
  • jsdocs: All public APIs documented
  • README: README and/or documentation topic updated
  • Design: For significant features, design document added to design folder
• Title and Description
  • Change type: title prefixed with fix, feat and module name in parens, which will appear in changelog
  • Title: use lower-case and doesn't end with a period
  • Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
  • Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"
• Sensitive Modules (requires 2 PR approvers)
  • IAM Policy Document (in @aws-cdk/aws-iam)
  • EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
  • Grant APIs (only if not based on official documentation with a reference)

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.