docs: update skaffold examples and documentation to properly reflect v1 ->v2 artifactOverrides changes - 2nd attempt (#8019)

Author: aaron-prindle

docs-v2/content/en/docs/pipeline-stages/deployers/helm.md

@@ -54,18 +54,18 @@ Associating the Helm image key allows Skaffold to track the image being built, a
 ```yaml
 build:
   artifacts:
-    - image: gcr.io/my-project/my-image # must match in artifactOverrides
+    - image: gcr.io/my-project/my-image # must match in setValues
 deploy:
   helm:
     releases:
     - name: my-release
-      artifactOverrides:
+      setValues:
         image: gcr.io/my-project/my-image # no tag present!
       imageStrategy:
         helm: {}
 ```
 
-The `artifactOverrides` binds a Helm value key to a build artifact.  The `imageStrategy` configures the image reference strategy for informing Helm of the image reference to a newly built artifact.
+The `setValues` configuration binds a Helm key to the specified value.  The `imageStrategy` configures the image reference strategy for informing Helm of the image reference to a newly built artifact.
 
 ### Multiple image overrides
 
@@ -89,7 +89,7 @@ deploy:
   helm:
     releases:
     - name: my-release
-      artifactOverrides:
+      setValues:
         firstContainerImage: gcr.io/my-project/first-image # no tag present!
         secondContainerImage: gcr.io/my-project/second-image # no tag present!
       imageStrategy:

examples/helm-deployment/skaffold.yaml

@@ -8,3 +8,5 @@ deploy:
     releases:
     - name: skaffold-helm
       chartPath: charts
+      setValues:
+        image: skaffold-helm