Support status subresource in CRDs

# Summary
Support the `status` subresource in CRDs of Argo Workflows.

# Use Cases
When using `karmada-control-plane` to propagate `workflow`, the `.status` can't be updated successfully.
If users wants to integrate `argo-workflow` with `karmada`, users needs to manually change the CRD of `workflow` in the karmada-control-plane cluster to make the `status` subresource available.
related to #10963

---

**Message from the maintainers**:

Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

Start by locating the Argo Workflows CRD definitions and the code or manifests that generate or register them, then review the status-update behavior described for karmada-control-plane and related issue #10963. Done means workflow status updates propagate successfully without manually editing the CRD to expose the status subresource.

Written by the indexing model from the issue text.