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 1452
git switch -c fix-pr-1452 && git push -u origin HEAD
gh pr create -t "fix: PR #1452" --body "Fixes https://github.com/cdklabs/awscdk-service-spec/pull/1452"

[github-actions]

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

├[~] service aws-autoscaling
│ └ resources
│    └[~] resource AWS::AutoScaling::AutoScalingGroup
│      ├ properties
│      │  └ CapacityReservationSpecification: (documentation changed)
│      └ types
│         ├[~] type BaselinePerformanceFactorsRequest
│         │ ├  - documentation: undefined
│         │ │  + documentation: The baseline performance to consider, using an instance family as a baseline reference. The instance family establishes the lowest acceptable level of performance. Auto Scaling uses this baseline to guide instance type selection, but there is no guarantee that the selected instance types will always exceed the baseline for every application.
│         │ │  Currently, this parameter only supports CPU performance as a baseline performance factor. For example, specifying `c6i` uses the CPU performance of the `c6i` family as the baseline reference.
│         │ └ properties
│         │    └ Cpu: (documentation changed)
│         ├[~] type CapacityReservationSpecification
│         │ ├  - documentation: undefined
│         │ │  + documentation: Describes the Capacity Reservation preference and targeting options. If you specify `open` or `none` for `CapacityReservationPreference` , do not specify a `CapacityReservationTarget` .
│         │ └ properties
│         │    ├ CapacityReservationPreference: (documentation changed)
│         │    └ CapacityReservationTarget: (documentation changed)
│         ├[~] type CapacityReservationTarget
│         │ ├  - documentation: undefined
│         │ │  + documentation: The target for the Capacity Reservation. Specify Capacity Reservations IDs or Capacity Reservation resource group ARNs.
│         │ └ properties
│         │    ├ CapacityReservationIds: (documentation changed)
│         │    └ CapacityReservationResourceGroupArns: (documentation changed)
│         ├[~] type CpuPerformanceFactorRequest
│         │ ├  - documentation: undefined
│         │ │  + documentation: The CPU performance to consider, using an instance family as the baseline reference.
│         │ └ properties
│         │    └ References: (documentation changed)
│         ├[~] type InstanceRequirements
│         │ └ properties
│         │    └ BaselinePerformanceFactors: (documentation changed)
│         └[~] type PerformanceFactorReferenceRequest
│           ├  - documentation: undefined
│           │  + documentation: Specify an instance family to use as the baseline reference for CPU performance. All instance types that All instance types that match your specified attributes will be compared against the CPU performance of the referenced instance family, regardless of CPU manufacturer or architecture differences.
│           │  > Currently only one instance family can be specified in the list.
│           └ properties
│              └ InstanceFamily: (documentation changed)
├[~] service aws-cloudfront
│ └ resources
│    ├[~] resource AWS::CloudFront::Distribution
│    │ └ types
│    │    └[~] type Logging
│    │      ├  - documentation: A complex type that controls whether access logs are written for the distribution.
│    │      │  + documentation: A complex type that specifies whether access logs are written for the distribution.
│    │      │  > If you already enabled standard logging (legacy) and you want to enable standard logging (v2) to send your access logs to Amazon S3, we recommend that you specify a *different* Amazon S3 bucket or use a *separate path* in the same bucket (for example, use a log prefix or partitioning). This helps you keep track of which log files are associated with which logging subscription and prevents log files from overwriting each other. For more information, see [Standard logging (access logs)](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/AccessLogs.html) in the *Amazon CloudFront Developer Guide* .
│    │      └ properties
│    │         └ Bucket: (documentation changed)
│    └[~] resource AWS::CloudFront::StreamingDistribution
│      └ types
│         └[~] type Logging
│           └ properties
│              └ Bucket: (documentation changed)
├[~] service aws-ecs
│ └ resources
│    └[~] resource AWS::ECS::Service
│      ├ properties
│      │  └ AvailabilityZoneRebalancing: (documentation changed)
│      └ types
│         └[~] type DeploymentController
│           └  - documentation: The deployment controller to use for the service. For more information, see [Amazon ECS deployment types](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deployment-types.html) in the *Amazon Elastic Container Service Developer Guide* .
│              + documentation: The deployment controller to use for the service.
├[~] service aws-lambda
│ └ resources
│    ├[~] resource AWS::Lambda::EventInvokeConfig
│    │ ├ properties
│    │ │  └ DestinationConfig: (documentation changed)
│    │ └ types
│    │    ├[~] type OnFailure
│    │    │ └ properties
│    │    │    └ Destination: (documentation changed)
│    │    └[~] type OnSuccess
│    │      └  - documentation: A destination for events that were processed successfully.
│    │         + documentation: A destination for events that were processed successfully.
│    │         To retain records of successful [asynchronous invocations](https://docs.aws.amazon.com/lambda/latest/dg/invocation-async.html#invocation-async-destinations) , you can configure an Amazon SNS topic, Amazon SQS queue, Lambda function, or Amazon EventBridge event bus as the destination.
│    └[~] resource AWS::Lambda::EventSourceMapping
│      └ types
│         └[~] type OnFailure
│           └ properties
│              └ Destination: (documentation changed)
├[~] service aws-rds
│ └ resources
│    ├[~] resource AWS::RDS::DBCluster
│    │ └ types
│    │    └[~] type ServerlessV2ScalingConfiguration
│    │      └ properties
│    │         └ MinCapacity: (documentation changed)
│    └[~] resource AWS::RDS::GlobalCluster
│      ├ properties
│      │  └ GlobalEndpoint: (documentation changed)
│      └ types
│         └[~] type GlobalEndpoint
│           ├  - documentation: undefined
│           │  + documentation: The writer endpoint for the new global database cluster. This endpoint always points to the writer DB instance in the current primary cluster.
│           └ properties
│              └ Address: (documentation changed)
└[~] service aws-route53resolver
  └ resources
     └[~] resource AWS::Route53Resolver::FirewallRuleGroup
       └ types
          └[~] type FirewallRule
            └ properties
               ├ ConfidenceThreshold: (documentation changed)
               ├ DnsThreatProtection: (documentation changed)
               └ FirewallThreatProtectionId: (documentation changed)