Add multi-stage Dockerfile target

The image push action publishes the following images:
- `rancher/hardened-sriov-network-operator`
- `rancher/hardened-sriov-network-config-daemon`
- `rancher/hardened-sriov-network-webhook`

On release these are built as `operator` image when instead they
should build using their own respective image stage targets

Fixup for 1e9cd69
Signed-off-by: Michael Fritch <[email protected]>

.github/workflows/image-push.yml

@@ -48,6 +48,7 @@ jobs:
         context: .
         push: true
         tags: rancher/hardened-sriov-network-operator:${{ github.event.release.tag_name }}
+        target: operator
         file: Dockerfile
         platforms: linux/amd64, linux/arm64
         build-args: |
@@ -59,6 +60,7 @@ jobs:
         context: .
         push: true
         tags: rancher/hardened-sriov-network-config-daemon:${{ github.event.release.tag_name }}
+        target: config-daemon
         file: Dockerfile
         platforms: linux/amd64, linux/arm64
         build-args: |
@@ -70,6 +72,7 @@ jobs:
         context: .
         push: true
         tags: rancher/hardened-sriov-network-webhook:${{ github.event.release.tag_name }}
+        target: webhook
         file: Dockerfile
         platforms: linux/amd64, linux/arm64
         build-args: |