Fix go list cmd

[nilekhc]

What steps did you take and what happened: [A clear and concise description of what the bug is.] Ref - https://github.com/kubernetes-sigs/secrets-store-sync-controller/pull/30#discussion_r1678720112

What did you expect to happen:

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Which provider are you using: [e.g. Azure Key Vault, HashiCorp Vault, etc. Have you checked out the provider's repo for more help?]

Environment:

• Secrets Store Sync Controller version: (use the image tag):
• Kubernetes version: (use kubectl version):

/assign

[nilekhc]

/good-first-issue

[k8s-ci-robot]

@nilekhc: This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-good-first-issue command.

In response to [this](https://github.com/kubernetes-sigs/secrets-store-sync-controller/issues/42): >/good-first-issue Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[nilekhc]

/unassign

[omerap12]

/assign