Add include Root CA on PKI syncs docs

docs/documentation/platform/pki/certificate-syncs/aws-secrets-manager.mdx

@@ -41,6 +41,7 @@ Any role with these permissions would work such as a custom policy with **Secret
 
             - **Enable Removal of Expired/Revoked Certificates**: If enabled, Infisical will remove certificates from the destination if they are no longer active in Infisical.
             - **Preserve Secret on Renewal**: Only applies to certificate renewals. When a certificate is renewed in Infisical, this option controls how the renewed certificate is handled. If enabled, the renewed certificate will update the existing secret, preserving the same secret name. If disabled, the renewed certificate will be created as a new secret with a new name.
+            - **Include Root CA**: If enabled, the Root CA certificate will be included in the certificate chain when syncing to AWS Secrets Manager. If disabled, only intermediate certificates will be included.
             - **Certificate Name Schema** (Optional): Customize how secret names are generated in AWS Secrets Manager. Use `{{certificateId}}` as a placeholder for the certificate ID.
             - **Auto-Sync Enabled**: If enabled, certificates will automatically be synced when changes occur. Disable to enforce manual syncing only.
 
@@ -119,6 +120,7 @@ Any role with these permissions would work such as a custom policy with **Secret
                 "canRemoveCertificates": true,
                 "preserveSecretOnRenewal": true,
                 "canImportCertificates": false,
+                "includeRootCa": false,
                 "certificateNameSchema": "myapp-{{certificateId}}",
                 "fieldMappings": {
                     "certificate": "ssl_cert",
@@ -152,6 +154,7 @@ Any role with these permissions would work such as a custom policy with **Secret
                 "canRemoveCertificates": true,
                 "preserveSecretOnRenewal": true,
                 "canImportCertificates": false,
+                "includeRootCa": false,
                 "certificateNameSchema": "infisical-{{certificateId}}",
                 "fieldMappings": {
                     "certificate": "certificate",
@@ -184,6 +187,7 @@ Any role with these permissions would work such as a custom policy with **Secret
                     "canRemoveCertificates": true,
                     "preserveSecretOnRenewal": true,
                     "canImportCertificates": false,
+                    "includeRootCa": false,
                     "certificateNameSchema": "myapp-{{certificateId}}",
                     "fieldMappings": {
                         "certificate": "ssl_cert",