fix: increase rollout timeout and add wait before pod exec in pod-identity intro

Author: svennam92

website/docs/fastpaths/developer/amazon-eks-pod-identity/introduction.md

@@ -7,7 +7,7 @@ The `carts` component of our architecture uses Amazon DynamoDB as its storage ba
 
 You can see this by running the following command:
 
-```bash
+```bash wait=30
 $ kubectl -n carts get pod
 NAME                              READY   STATUS    RESTARTS        AGE
 carts-5d7fc9d8f-xm4hs             1/1     Running   0               14m

website/docs/fastpaths/developer/pod-logging/fluent-bit-cloudwatch.md

@@ -8,10 +8,10 @@ In this lab exercise, we'll see how to check the Kubernetes pod logs forwarded b
 
 First, lets recycle the pods for the `ui` component to make sure fresh logs are written since we enabled Fluent Bit.
 
-```bash
+```bash timeout=180
 $ kubectl delete pod -n ui --all
 $ kubectl rollout status deployment/ui \
-  -n ui --timeout 30s
+  -n ui --timeout 120s
 deployment "ui" successfully rolled out
 ```
 

website/docs/fastpaths/operator/amazon-eks-pod-identity/introduction.md

@@ -7,7 +7,7 @@ The `carts` component of our architecture uses Amazon DynamoDB as its storage ba
 
 You can see this by running the following command:
 
-```bash
+```bash wait=30
 $ kubectl -n carts get pod
 NAME                              READY   STATUS    RESTARTS        AGE
 carts-5d7fc9d8f-xm4hs             1/1     Running   0               14m