fix: Fixes utility ls may return 503 in certain situation

Type of change

• Bug Fix
• Feature
• Pipeline
• Test

Does this introduce a change in the core logic?

• No
• Yes

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• GCP
• IBM

Does this follow conventional commits spec?

• No
• Yes

Have you set the target Milestone?

• No
• Yes

Have you set the no-detached-pipeline label?

• No
• Yes

Updates description?

Fixes an issue that when utility ls was listing datasets from geo solution, it will return 503.