Description of problem: destroy hypershift on CLI using -secret-creds secret-name with -namespace the-namespace, it cannot find the secret. When I use --aws-creds and point to the local AWS CLI credential file, the destroy proceeds.

Version-Release number of selected component (if applicable): ACM 2.8.1 / MCE 2.3.1

How reproducible: every time.

Steps to Reproduce:

1. create a hosted cluster on AWS using --secret-creds secret-name with --namespace the-namespace of the secret
2. attempt to destroy the hosted cluster by specifying the same ^^
3. get a failure like:

hypershift destroy cluster aws --name sberens-hcp-aws-west --infra-id sberens-hcp-aws-west-nkljh --secret-creds sberens-aws --namespace demo-credentials --base-domain bu.red-chesterfield.com --destroy-cloud-resources --region us-west-2
2023-09-20T11:58:34-05:00 INFO Retreiving credentials secret {"namespace": "demo-credentials", "name": "sberens-aws"}
Error: secrets "sberens-aws" not found
secrets "sberens-aws" not found

for sure the secret is valid;

Actual results: Error: secrets "sberens-aws" not found secrets "sberens-aws" not found. Destroy will not work. Alternative/workaround, I use the --aws-creds ~/.aws/credentials syntax instead

Expected results: 

I expect the destroy to make use of the AWS credentials in the secret stored in the namespace

Additional info: