bugfix: update binding status when work's applied condition status changed

[mrlihanbo]

Signed-off-by: lihanbo lihanbo2@huawei.com

What type of PR is this?
/kind bug

What this PR does / why we need it:
When execution controller update resource failed, the work's fully applied condition will be set to False, but the ManifestStatuses won't be changed(as updated failed). Under this circumstance，binding controller also need to aggregate work status.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

`karmada-controller-manager`: Fixed RB/CRB controller can't aggregate status in case of work condition update issue.

[mrlihanbo]

To reproduce:
step1. create a nodeport service using 30000 nodePort in member1 cluster:

apiVersion: v1
kind: Service
metadata:
  name: my-service-member1
spec:
  type: NodePort
  selector:
    app: MyApp
  ports:
    - port: 80
      targetPort: 80
      nodePort: 30000

step2: create a nodeport service using 30001 nodePort in karmada

apiVersion: v1
kind: Service
metadata:
  name: my-service-karmada
spec:
  type: NodePort
  selector:
    app: MyApp
  ports:
    - port: 80
      targetPort: 80
      nodePort: 30001

step3: create propagation policy:

apiVersion: policy.karmada.io/v1alpha1
kind: PropagationPolicy
metadata:
  name: my-service
spec:
  resourceSelectors:
    - apiVersion: v1
      kind: Service
      name: my-service
  placement:
    clusterAffinity:
      clusterNames:
        - member1
        - member2

step4: update nodePort of karmada service to 30000. Then you will found the work is propagated faied, but status in resource binding is not correct.
work status:

status:
  conditions:
  - lastTransitionTime: "2022-03-22T01:16:31Z"
    message: 'Failed to apply all manifests (0/1): Service "my-service" is invalid:
      spec.ports[0].nodePort: Invalid value: 30000: provided port is already allocated'
    reason: AppliedFailed
    status: "False"
    type: Applied
  manifestStatuses:
  - identifier:
      kind: Service
      name: my-service
      namespace: default
      ordinal: 0
      resource: ""
      version: v1
    status:
      loadBalancer: {}

binding status:

status:
  aggregatedStatus:
  - applied: true
    clusterName: member2
    status:
      loadBalancer: {}
  - applied: true
    clusterName: member1
    status:
      loadBalancer: {}
  conditions:
  - lastTransitionTime: "2022-03-22T01:18:23Z"
    message: All works have been successfully applied
    reason: FullyAppliedSuccess
    status: "True"
    type: FullyApplied
  - lastTransitionTime: "2022-03-22T01:18:23Z"
    message: Binding has been scheduled
    reason: BindingScheduled
    status: "True"
    type: Scheduled

[mrlihanbo]

/cc @XiShanYongYe-Chang

[XiShanYongYe-Chang]

/lgtm

/cc @RainbowMango

[Garrybest]

/lgtm

[RainbowMango]

/approve

@mrlihanbo
Please help cherry-pick this patch to both release-1.0 and release-1.1.

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RainbowMango

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [RainbowMango]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment