docs: Add CI/CD example for building Argo Workflows. Closes argoproj#…

…8591

This commit introduces a detailed example for implementing CI/CD pipelines to build Argo Workflows using Argo Workflows:

- **CI**: Includes steps for initializing builds via webhook, building the CLI, using Buildkit for image builds, running tests, collecting coverage reports, deploying to a cluster, and executing basic E2E tests.
- **CD**: Covers tagging, updating manifests with kustomize, committing updates, and initiating an Argo CD sync.
- **Pipeline**: Integrates CI and CD jobs with an approval step.

Signed-off-by: Wesley Scholl <[email protected]>
Signed-off-by: Wesley Scholl <[email protected]>

examples/ci-cd-workflow.yaml

@@ -1,7 +1,7 @@
 # Argo Workflows - CI/CD Setup Guide
 #
 # Overview:
-# To run this workflow end-to-end, configure the following components.
+# To run this CI/CD workflow end-to-end, configure the following components:
 #
 
 # 1. WorkflowEventBinding
@@ -26,6 +26,10 @@
 #
 # - Auth Token: Required in the `Authorization` header to trigger WorkflowEventBinding. Follow these steps to create an access token: https://argo-workflows.readthedocs.io/en/latest/access-token/
 #
+# - The payload is based on a GitHub webhook event. For more information on the payload, see the GitHub webhook documentation: https://docs.github.com/en/developers/webhooks-and-events/webhook-events-and-payloads
+#
+# - This workflow focuses on the WorkflowEventBinding setup. To trigger using Argo Events, refer to the Argo Events documentation: https://argoproj.github.io/argo-events/
+#
 
 # 2. Docker Configuration
 #