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

[github-actions]

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

├[~] service aws-appstream
│ └ resources
│    ├[~] resource AWS::AppStream::AppBlock
│    │ └ types
│    │    └[~] type Tag
│    │      └  - documentation: undefined
│    │         + documentation: The tag of the app block.
│    ├[~] resource AWS::AppStream::Application
│    │ └ types
│    │    └[~] type Tag
│    │      └  - documentation: undefined
│    │         + documentation: The tag of the application.
│    └[~] resource AWS::AppStream::Fleet
│      ├ properties
│      │  └ MaxSessionsPerInstance: (documentation changed)
│      └ types
│         └[~] type ComputeCapacity
│           └ properties
│              └ DesiredSessions: (documentation changed)
├[~] service aws-cloudformation
│ └ resources
│    ├[~] resource AWS::CloudFormation::StackSet
│    │ └ properties
│    │    ├ StackSetName: (documentation changed)
│    │    ├ Tags: (documentation changed)
│    │    └ TemplateBody: (documentation changed)
│    └[~] resource AWS::CloudFormation::WaitConditionHandle
│      └ attributes
│         └ Id: (documentation changed)
├[~] service aws-codepipeline
│ └ resources
│    └[~] resource AWS::CodePipeline::Pipeline
│      └  - documentation: The `AWS::CodePipeline::Pipeline` resource creates a CodePipeline pipeline that describes how software changes go through a release process. For more information, see [What Is CodePipeline?](https://docs.aws.amazon.com/codepipeline/latest/userguide/welcome.html) in the *AWS CodePipeline User Guide* .
│         + documentation: The `AWS::CodePipeline::Pipeline` resource creates a CodePipeline pipeline that describes how software changes go through a release process. For more information, see [What Is CodePipeline?](https://docs.aws.amazon.com/codepipeline/latest/userguide/welcome.html) in the *AWS CodePipeline User Guide* .
│         > V2 type pipelines, along with triggers on Git tags and pipeline-level variables, are not currently supported for CloudFormation and CDK resources in CodePipeline. For more information about V2 type pipelines, see [Pipeline types](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipeline-types.html) in the *AWS CodePipeline User Guide* .
├[~] service aws-eks
│ └ resources
│    └[~] resource AWS::EKS::Cluster
│      ├ properties
│      │  └ ResourcesVpcConfig: (documentation changed)
│      └ types
│         └[~] type ResourcesVpcConfig
│           └ properties
│              └ SubnetIds: (documentation changed)
├[~] service aws-internetmonitor
│ └ resources
│    └[~] resource AWS::InternetMonitor::Monitor
│      └ types
│         ├[~] type InternetMeasurementsLogDelivery
│         │ └ properties
│         │    └ S3Config: (documentation changed)
│         └[~] type S3Config
│           ├  - documentation: The configuration for publishing Amazon CloudWatch Internet Monitor internet measurements to Amazon S3. The configuration includes the bucket name and (optionally) prefix for the S3 bucket to store the measurements, and the delivery status. The delivery status is `ENABLED` or `DISABLED` , depending on whether you choose to deliver internet measurements to S3 logs.
│           │  + documentation: The configuration for publishing Amazon CloudWatch Internet Monitor internet measurements to Amazon S3. The configuration includes the bucket name and (optionally) bucket prefix for the S3 bucket to store the measurements, and the delivery status. The delivery status is `ENABLED` if you choose to deliver internet measurements to S3 logs, and `DISABLED` otherwise.
│           │  The measurements are also published to Amazon CloudWatch Logs.
│           └ properties
│              ├ BucketName: (documentation changed)
│              ├ BucketPrefix: (documentation changed)
│              └ LogDeliveryStatus: (documentation changed)
├[~] service aws-msk
│ └ resources
│    ├[~] resource AWS::MSK::Cluster
│    │ └ types
│    │    └[~] type BrokerNodeGroupInfo
│    │      └ properties
│    │         └ InstanceType: (documentation changed)
│    └[~] resource AWS::MSK::Replicator
│      └ attributes
│         └ ReplicatorArn: (documentation changed)
├[~] service aws-networkmanager
│ └ resources
│    └[~] resource AWS::NetworkManager::Device
│      └ attributes
│         └ CreatedAt: (documentation changed)
└[~] service aws-rolesanywhere
  └ resources
     ├[~] resource AWS::RolesAnywhere::Profile
     │ ├  - documentation: Creates a Profile.
     │ │  + documentation: Creates a *profile* , a list of the roles that Roles Anywhere service is trusted to assume. You use profiles to intersect permissions with IAM managed policies.
     │ │  *Required permissions:* `rolesanywhere:CreateProfile` .
     │ └ properties
     │    ├ DurationSeconds: (documentation changed)
     │    ├ Enabled: (documentation changed)
     │    ├ ManagedPolicyArns: (documentation changed)
     │    ├ Name: (documentation changed)
     │    ├ RequireInstanceProperties: (documentation changed)
     │    ├ RoleArns: (documentation changed)
     │    ├ SessionPolicy: (documentation changed)
     │    └ Tags: (documentation changed)
     └[~] resource AWS::RolesAnywhere::TrustAnchor
       ├  - documentation: Creates a TrustAnchor.
       │  + documentation: Creates a trust anchor to establish trust between IAM Roles Anywhere and your certificate authority (CA). You can define a trust anchor as a reference to an AWS Private Certificate Authority ( AWS Private CA ) or by uploading a CA certificate. Your AWS workloads can authenticate with the trust anchor using certificates issued by the CA in exchange for temporary AWS credentials.
       │  *Required permissions:* `rolesanywhere:CreateTrustAnchor` .
       └ types
          ├[~] type Source
          │ ├  - documentation: Object representing the TrustAnchor type and its related certificate data.
          │ │  + documentation: The trust anchor type and its related certificate data.
          │ └ properties
          │    ├ SourceData: (documentation changed)
          │    └ SourceType: (documentation changed)
          └[~] type SourceData
            └  - documentation: A union object representing the data field of the TrustAnchor depending on its type
               + documentation: The data field of the trust anchor depending on its type.