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

[github-actions]

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

├[~] service aws-bedrock
│ └ resources
│    ├[~]  resource AWS::Bedrock::DataSource
│    │  └ types
│    │     ├[~] type BedrockDataAutomationConfiguration
│    │     │ ├      - documentation: Settings for a Bedrock Data Automation used to parse documents for a data source.
│    │     │ │      + documentation: Contains configurations for using Amazon Bedrock Data Automation as the parser for ingesting your data sources.
│    │     │ └ properties
│    │     │    └ ParsingModality: (documentation changed)
│    │     ├[~] type BedrockFoundationModelConfiguration
│    │     │ └ properties
│    │     │    └ ParsingModality: (documentation changed)
│    │     └[~] type ParsingConfiguration
│    │       └ properties
│    │          └ BedrockDataAutomationConfiguration: (documentation changed)
│    └[~]  resource AWS::Bedrock::KnowledgeBase
│       └ types
│          ├[~] type KendraKnowledgeBaseConfiguration
│          │ ├      - documentation: Configurations for a Kendra knowledge base
│          │ │      + documentation: Settings for an Amazon Kendra knowledge base.
│          │ └ properties
│          │    └ KendraIndexArn: (documentation changed)
│          ├[~] type KnowledgeBaseConfiguration
│          │ └ properties
│          │    └ KendraKnowledgeBaseConfiguration: (documentation changed)
│          ├[~] type S3Location
│          │ ├      - documentation: An Amazon S3 location.
│          │ │      + documentation: A storage location in an S3 bucket.
│          │ └ properties
│          │    └ URI: (documentation changed)
│          ├[~] type SupplementalDataStorageConfiguration
│          │ └      - documentation: Configurations for supplemental data storage.
│          │        + documentation: Specifies configurations for the storage location of the images extracted from multimodal documents in your data source. These images can be retrieved and returned to the end user.
│          ├[~] type SupplementalDataStorageLocation
│          │ ├      - documentation: Supplemental data storage location.
│          │ │      + documentation: Contains information about a storage location for images extracted from multimodal documents in your data source.
│          │ └ properties
│          │    └ S3Location: (documentation changed)
│          └[~] type VectorKnowledgeBaseConfiguration
│            └ properties
│               └ SupplementalDataStorageConfiguration: (documentation changed)
├[~] service aws-cloudformation
│ └ resources
│    ├[~]  resource AWS::CloudFormation::GuardHook
│    │  └      - documentation: The `AWS::CloudFormation::GuardHook` resource creates a Guard Hook. Using the Guard domain specific language (DSL), you can author Guard Hooks to evaluate your resources before allowing stack operations.
│    │         For more information, see [Guard Hooks](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/guard-hooks.html) in the *AWS CloudFormation Hooks User Guide* .
│    │         + documentation: The `AWS::CloudFormation::GuardHook` resource creates and activates a Guard Hook. Using the Guard domain specific language (DSL), you can author Guard Hooks to evaluate your resources before allowing stack operations.
│    │         For more information, see [Guard Hooks](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/guard-hooks.html) in the *AWS CloudFormation Hooks User Guide* .
│    ├[~]  resource AWS::CloudFormation::LambdaHook
│    │  └      - documentation: The `AWS::CloudFormation::LambdaHook` resource creates a Lambda Hook. You can use a Lambda Hook to evaluate your resources before allowing stack operations. This resource forwards requests for resource evaluation to a Lambda function.
│    │         For more information, see [Lambda Hooks](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/lambda-hooks.html) in the *AWS CloudFormation Hooks User Guide* .
│    │         + documentation: The `AWS::CloudFormation::LambdaHook` resource creates and activates a Lambda Hook. You can use a Lambda Hook to evaluate your resources before allowing stack operations. This resource forwards requests for resource evaluation to a Lambda function.
│    │         For more information, see [Lambda Hooks](https://docs.aws.amazon.com/cloudformation-cli/latest/hooks-userguide/lambda-hooks.html) in the *AWS CloudFormation Hooks User Guide* .
│    ├[~]  resource AWS::CloudFormation::Stack
│    │  └ properties
│    │     └ TemplateURL: (documentation changed)
│    └[~]  resource AWS::CloudFormation::StackSet
│       └ properties
│          └ TemplateURL: (documentation changed)
└[~] service aws-eks
  └ resources
     └[~]  resource AWS::EKS::IdentityProviderConfig
        └      - documentation: Associates an identity provider configuration to a cluster.
               If you want to authenticate identities using an identity provider, you can create an identity provider configuration and associate it to your cluster. After configuring authentication to your cluster you can create Kubernetes `Role` and `ClusterRole` objects, assign permissions to them, and then bind them to the identities using Kubernetes `RoleBinding` and `ClusterRoleBinding` objects. For more information see [Using RBAC Authorization](https://docs.aws.amazon.com/https://Kubernetes.io/docs/reference/access-authn-authz/rbac/) in the Kubernetes documentation.
               + documentation: Associates an identity provider configuration to a cluster.
               If you want to authenticate identities using an identity provider, you can create an identity provider configuration and associate it to your cluster. After configuring authentication to your cluster you can create Kubernetes `Role` and `ClusterRole` objects, assign permissions to them, and then bind them to the identities using Kubernetes `RoleBinding` and `ClusterRoleBinding` objects. For more information see [Using RBAC Authorization](https://docs.aws.amazon.com/https://kubernetes.io/docs/reference/access-authn-authz/rbac/) in the Kubernetes documentation.