docs: docs for ID and slug support across all operator CRDS

docs/integrations/platforms/kubernetes/infisical-dynamic-secret-crd.mdx

@@ -223,7 +223,8 @@ spec:
   spec:
     dynamicSecret:
       secretName: <dynamic-secret-name>
-      projectId: <project-id>
+      projectId: <project-id> # Either projectId or projectSlug is required
+      projectSlug: <project-slug>
       environmentSlug: <env-slug>
       secretsPath: <secrets-path>
   ```
@@ -238,8 +239,21 @@ spec:
 
 <Accordion title="dynamicSecret.projectId">
   The project ID of where the dynamic secret is stored in Infisical.
+
+  <Note>
+    Please note that you can only use either `projectId` or `projectSlug` in the `dynamicSecret` field.
+  </Note>
 </Accordion>
 
+<Accordion title="dynamicSecret.projectSlug">
+  The project slug of where the dynamic secret is stored in Infisical.
+
+  <Note>
+    Please note that you can only use either `projectId` or `projectSlug` in the `dynamicSecret` field.
+  </Note>
+</Accordion>
+
+
 {" "}
 
 <Accordion title="dynamicSecret.environmentSlug">

docs/integrations/platforms/kubernetes/infisical-push-secret-crd.mdx

@@ -44,7 +44,8 @@ Before applying the InfisicalPushSecret CRD, you need to create a Kubernetes sec
     deletionPolicy: Delete # If set to delete, the secret(s) inside Infisical managed by the operator, will be deleted if the InfisicalPushSecret CRD is deleted.
 
     destination:
-      projectId: <project-id>
+      projectId: <project-id> # Either projectId or projectSlug is required
+      projectSlug: <project-slug>
       environmentSlug: <env-slug>
       secretsPath: <secret-path>
 
@@ -203,6 +204,18 @@ After applying the InfisicalPushSecret CRD, you should notice that the secrets y
 
   <Accordion title="destination.projectId">
     The project ID where you want to create the secrets in Infisical.
+
+    <Note>
+      Please note that you can only use either `projectId` or `projectSlug` in the `destination` field.
+    </Note>
+  </Accordion>
+
+  <Accordion title="destination.projectSlug">
+    The project slug where you want to create the secrets in Infisical.
+
+    <Note>
+      Please note that you can only use either `projectId` or `projectSlug` in the `destination` field.
+    </Note>
   </Accordion>
 
   <Accordion title="destination.environmentSlug">

docs/integrations/platforms/kubernetes/infisical-secret-crd.mdx

@@ -142,7 +142,10 @@ spec:
   authentication:
       universalAuth:
           secretsScope:
+              # either projectSlug or projectId is required
               projectSlug: <project-slug> # <-- project slug
+              projectId: <project-id> # <-- project id
+
               envSlug: <env-slug> # "dev", "staging", "prod", etc..
               secretsPath: "<secrets-path>" # Root is "/"
           credentialsRef:
@@ -496,9 +499,11 @@ spec:
 
     <Info>
       Make sure to also populate the `secretsScope` field with the project slug
-      _`projectSlug`_, environment slug _`envSlug`_, and secrets path
+      _`projectSlug`_, or project ID _`projectId`_, environment slug _`envSlug`_, and secrets path
       _`secretsPath`_ that you want to fetch secrets from. Please see the example
       below.
+
+      Please note that you can only use either `projectSlug` or `projectId` in the `secretsScope` field.
     </Info>
 
     ## Example
@@ -545,9 +550,11 @@ spec:
 
 <Info>
   Make sure to also populate the `secretsScope` field with the project slug
-  _`projectSlug`_, environment slug _`envSlug`_, and secrets path
+  _`projectSlug`_, or project ID _`projectId`_, environment slug _`envSlug`_, and secrets path
   _`secretsPath`_ that you want to fetch secrets from. Please see the example
   below.
+
+  Please note that you can only use either `projectSlug` or `projectId` in the `secretsScope` field.
 </Info>
 
 ## Example
@@ -588,9 +595,11 @@ spec:
 
 <Info>
   Make sure to also populate the `secretsScope` field with the project slug
-  _`projectSlug`_, environment slug _`envSlug`_, and secrets path
+  _`projectSlug`_, or project ID _`projectId`_, environment slug _`envSlug`_, and secrets path
   _`secretsPath`_ that you want to fetch secrets from. Please see the example
   below.
+
+  Please note that you can only use either `projectSlug` or `projectId` in the `secretsScope` field.
 </Info>
 
 ## Example
@@ -631,9 +640,11 @@ spec:
 
 <Info>
   Make sure to also populate the `secretsScope` field with the project slug
-  _`projectSlug`_, environment slug _`envSlug`_, and secrets path
+  _`projectSlug`_, or project ID _`projectId`_, environment slug _`envSlug`_, and secrets path
   _`secretsPath`_ that you want to fetch secrets from. Please see the example
   below.
+
+  Please note that you can only use either `projectSlug` or `projectId` in the `secretsScope` field.
 </Info>
 
 ## Example
@@ -675,9 +686,11 @@ spec:
 
 <Info>
   Make sure to also populate the `secretsScope` field with the project slug
-  _`projectSlug`_, environment slug _`envSlug`_, and secrets path
+  _`projectSlug`_, or project ID _`projectId`_, environment slug _`envSlug`_, and secrets path
   _`secretsPath`_ that you want to fetch secrets from. Please see the example
   below.
+
+  Please note that you can only use either `projectSlug` or `projectId` in the `secretsScope` field.
 </Info>
 
 ## Example
@@ -730,9 +743,11 @@ spec:
 
 <Info>
   Make sure to also populate the `secretsScope` field with the project slug
-  _`projectSlug`_, environment slug _`envSlug`_, and secrets path
+  _`projectSlug`_, or project ID _`projectId`_, environment slug _`envSlug`_, and secrets path
   _`secretsPath`_ that you want to fetch secrets from. Please see the example
   below.
+
+  Please note that you can only use either `projectSlug` or `projectId` in the `secretsScope` field.
 </Info>
 
 ## Example