work: name conflicts when different workloads have the same name

[Garrybest]

What happened:
When different workload have the same name, the work that creating by the ResourceBindingController will have the same name in one ExecutionSpaceName, which would cause execution chaos.

Reason: The work's name is the same with the resource binding, but it's namespace is associated with cluster. I suggest to adding namespace to generate works' name.

karmada/pkg/util/helper/binding.go

Lines 177 to 182 in 7a0d6c9

	workName := binding.GetName()
	workNamespace, err := names.GenerateExecutionSpaceName(clusterName)
	if err != nil {
	klog.Errorf("Failed to ensure Work for cluster: %s. Error: %v.", clusterName, err)
	return err
	}

What you expected to happen:
The work's name may contain namespace to distinguish with each other.

How to reproduce it (as minimally and precisely as possible):
For example:
I create 2 deployment in 2 different namespace but having the same name, only one work will be created. When I delete them, the member cluster also runs one of a deployment which may cause resource leak.

[root@garryfang /data/garryfang/karmada/samples/nginx]# kubectl get deployments.apps -A
NAMESPACE   NAME    READY   UP-TO-DATE   AVAILABLE   AGE
garrytest   nginx   2/2     2            2           23s
lynntest    nginx   10/10   10           10          84s

[root@garryfang /data/garryfang/karmada/samples/nginx]# kubectl get works.work.karmada.io -A
NAMESPACE            NAME                  AGE
karmada-es-member1   garrytest-namespace   23h
karmada-es-member1   lynntest-namespace    4d12h
karmada-es-member1   nginx-deployment      99s
karmada-es-member2   garrytest-namespace   23h
karmada-es-member2   lynntest-namespace    4d12h
karmada-es-member3   garrytest-namespace   23h
karmada-es-member3   lynntest-namespace    4d12h

Only one work exists.

Anything else we need to know?:

Environment:

• Karmada version: latest
• Others:

[Garrybest]

/assign @Garrybest

[RainbowMango]

/assign @Garrybest

Karmada bot not ready now, (it will be soon), manually assign to you :)

[RainbowMango]

LGTM.
cc @GitHubxsy @mrlihanbo

[mrlihanbo]

LGTM