fix: remove redundant KARMADA_PULL_CLUSTER_NAME exports in CLI installation workflow

Signed-off-by: Sky Singh <akashsingh2210670@gmail.com>

Author: SkySingh04

.github/workflows/installation-cli.yaml

@@ -45,7 +45,6 @@ jobs:
 
           # run a single e2e
           export PULL_BASED_CLUSTERS="member1:${HOME}/.kube/member1.config"  
-          export KARMADA_PULL_CLUSTER_NAME="member1" 
           export KUBECONFIG=${HOME}/.kube/karmada-host.config:${HOME}/karmada/karmada-apiserver.config
           GO111MODULE=on go install github.com/onsi/ginkgo/v2/ginkgo
           ginkgo -v --race --trace -p  --focus="[BasicPropagation] propagation testing deployment propagation testing"  ./test/e2e/suites/base
@@ -90,7 +89,6 @@ jobs:
           
           # run a single e2e
           export PULL_BASED_CLUSTERS="config-member1:${HOME}/.kube/config-member1.config"
-          export KARMADA_PULL_CLUSTER_NAME="config-member1"
           export KUBECONFIG=${HOME}/.kube/karmada-host.config:${HOME}/karmada/karmada-apiserver.config
           GO111MODULE=on go install github.com/onsi/ginkgo/v2/ginkgo
           ginkgo -v --race --trace -p  --focus="[BasicPropagation] propagation testing deployment propagation testing"  ./test/e2e/suites/base