Always build and load sds standard image for tests

[davidjumani]

Description

The glooctl istio inject command always injects the standard sds image variant irrespective of the variant of edge installed. As tests run on the distroless variant, this PR ensures the standard sds image is built and loaded so the glooctl test passes while we fix the underlying issue

Context

https://github.com/solo-io/gloo/actions/runs/8683582052/job/23826553002?pr=9358
https://solo-io-corp.slack.com/archives/G01EERAK3KJ/p1713193713670019

 Back-off pulling image "quay.io/solo-io/sds:1.0.0-ci1"
  Warning  Failed     30s (x3 over 56s)  kubelet            Error: ImagePullBackOff
  Warning  Failed     15s (x3 over 59s)  kubelet            Error: ErrImagePull
  Warning  Failed     15s (x3 over 59s)  kubelet            Failed to pull image "quay.io/solo-io/sds:1.0.0-ci1": rpc error: code = NotFound desc = failed to pull and unpack image "quay.io/solo-io/sds:1.0.0-ci1": failed to resolve reference "quay.io/solo-io/sds:1.0.0-ci1": quay.io/solo-io/sds:1.0.0-ci1: not found

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

[github-actions]

Visit the preview URL for this PR (updated for commit 840204c):

https://gloo-edge--pr9367-fix-glooctl-istio-in-d76qvbfm.web.app

_{(expires Tue, 23 Apr 2024 17:08:47 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 77c2b86e287749579b7ff9cadb81e099042ef677}

[davidjumani]

Followup issue #9372

[nfuden]

This is definitely hacky as we expect our tools like istio injection to be deciding on the right sds container type (fips, distorless, default). However given that we do not support this today I am ok with us building this non-distroless image to unblock our tests