Bug: worker/controller failed setup to on topology configuration on gke autopilot clusters

### 📜 Description

Bug

I tried setting up [kubeslice demo on cloud clusters](https://kubeslice.io/documentation/open-source/1.4.0/tutorials/kubeslice-cli-tutorials/kubeslice-cli-demo-on-cloud-clusters) on my two gke clusters in us-east1 and us-central1 , but though I couldn't able to make initial setup in my clusters via `kubeslice-cli --config=topology2.yml install` , also I tried the kind minimal-demo didn't worked out mentioned by https://github.com/kubeslice/kubeslice-cli/issues/83 , It seems gke autopilot cluster doesn't have any worker node by default and kubeslice-cli needs atleast a minimum of 1 node to each cluster

### 👟 Reproduction steps

- Create 3 GKE Autopilot clusters on same or different regions
- Manage to have a topology file of cluster and workers with its kubeconfig
- Finally run the installation using kubeslice-cli

### 👍 Expected behavior

Not working

### 👎 Actual Behavior

Its needs to actually work on GKE Autopilot clusters

### 🐚 Relevant log output

### Version

None

### 🖥️ What operating system are you seeing the problem on?

_No response_

### ✅ Proposed Solution

_No response_

### 👀 Have you spent some time to check if this issue has been raised before?

- [x] I checked and didn't find any similar issue

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

No source files or tests are named. Start by reproducing the `kubeslice-cli --config=topology2.yml install` flow with the described GKE Autopilot topology, and compare it with the minimal-demo context in issue 83. Done means the installation works on GKE Autopilot clusters with the reported topology.

Written by the indexing model from the issue text.