feat(sources): update documentation

[aws-cdk-automation]

⚠️ This Pull Request updates daily and will overwrite all manual changes pushed to the branch

Updates the documentation source from upstream. See details in workflow run.

---

Automatically created by projen via the "update-source-documentation" workflow

[github-actions]

To work on this Pull Request, please create a new branch and PR. This prevents your work from being deleted by the automation.

Run the following commands inside the repo:

gh co 1420
git switch -c fix-pr-1420 && git push -u origin HEAD
gh pr create -t "fix: PR #1420" --body "Fixes https://github.com/cdklabs/awscdk-service-spec/pull/1420"

[github-actions]

@aws-cdk/aws-service-spec: Model database diff detected

├[~] service aws-codebuild
│ └ resources
│    ├[~] resource AWS::CodeBuild::Fleet
│    │ └ properties
│    │    ├ ComputeType: (documentation changed)
│    │    └ EnvironmentType: (documentation changed)
│    └[~] resource AWS::CodeBuild::Project
│      └ types
│         └[~] type Environment
│           └ properties
│              └ ComputeType: (documentation changed)
├[~] service aws-datasync
│ └ resources
│    └[~] resource AWS::DataSync::Task
│      └ properties
│         └ TaskMode: (documentation changed)
├[~] service aws-ec2
│ └ resources
│    └[~] resource AWS::EC2::SecurityGroupVpcAssociation
│      ├  - documentation: Resource type definition for the AWS::EC2::SecurityGroupVpcAssociation resource
│      │  + documentation: A security group association with a VPC.
│      ├ properties
│      │  ├ GroupId: (documentation changed)
│      │  └ VpcId: (documentation changed)
│      └ attributes
│         ├ State: (documentation changed)
│         ├ StateReason: (documentation changed)
│         └ VpcOwnerId: (documentation changed)
├[~] service aws-elasticache
│ └ resources
│    └[~] resource AWS::ElastiCache::ReplicationGroup
│      └ properties
│         └ TransitEncryptionEnabled: (documentation changed)
├[~] service aws-lambda
│ └ resources
│    └[~] resource AWS::Lambda::Function
│      └ types
│         └[~] type Code
│           ├  - documentation: The [deployment package](https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-package.html) for a Lambda function. To deploy a function defined as a container image, you specify the location of a container image in the Amazon ECR registry. For a .zip file deployment package, you can specify the location of an object in Amazon S3. For Node.js and Python functions, you can specify the function code inline in the template.
│           │  Changes to a deployment package in Amazon S3 or a container image in ECR are not detected automatically during stack updates. To update the function code, change the object key or version in the template.
│           │  + documentation: The [deployment package](https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-package.html) for a Lambda function. To deploy a function defined as a container image, you specify the location of a container image in the Amazon ECR registry. For a .zip file deployment package, you can specify the location of an object in Amazon S3. For Node.js and Python functions, you can specify the function code inline in the template.
│           │  > When you specify source code inline for a Node.js function, the `index` file that AWS CloudFormation creates uses the extension `.js` . This means that Lambda treats the file as a CommonJS module. ES modules aren't supported for inline functions. 
│           │  Changes to a deployment package in Amazon S3 or a container image in ECR are not detected automatically during stack updates. To update the function code, change the object key or version in the template.
│           └ properties
│              └ ZipFile: (documentation changed)
└[~] service aws-logs
  └ resources
     └[~] resource AWS::Logs::Delivery
       └ properties
          ├ FieldDelimiter: (documentation changed)
          └ RecordFields: (documentation changed)