Refactor kubectl scale to patch scale subresource

[knight42]

What type of PR is this?
/kind feature

What this PR does / why we need it:
Currently kubectl scale would send a PUT request without ResourceVersion, which is introduced in #75210, and because of that custom resource cannot be scaled since custom resource could not be updated unconditionally.

Considered that PUT without resource version is not a best practice and we are not willing to do a GET before the request, so I choose to update kubectl to use PATCH instead of PUT.

Which issue(s) this PR fixes:
Part of #80515

Special notes for your reviewer:
Although I have created another PR to fix the problem, which requires changes on apiserver, the apiserver would not be updated as frequently as kubectl in reality, so it may be best to update both apiserver(make old kubectls work) and kubectl.

Does this PR introduce a user-facing change?:

kubectl could scale custom resource again

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

Hi @knight42. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[knight42]

/assign @seans3

cc @liggitt

[seans3]

/ok-to-test

[knight42]

/assign @smarterclayton

[knight42]

@seans3 @smarterclayton all tests passed now, PTAL

[xmudrii]

@seans3 @liggitt Ping. Can anyone help with reviewing this PR?

[dims]

/uncc

[seans3]

/cc @apelisse

for more context

[knight42]

/retest

[apelisse]

Few style nits, but otherwise looks good. Feel free to fix or not
/lgtm
/approve
/hold

[knight42]

@apelisse all fixed now

[apelisse]

Thanks, I think it looks much better this way,
/lgtm
/approve

[smarterclayton]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: apelisse, knight42, smarterclayton

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:

• staging/src/k8s.io/kubectl/OWNERS [apelisse,smarterclayton]
• test/OWNERS [smarterclayton]

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

[knight42]

@apelisse @smarterclayton would you mind unholding this PR?

[apelisse]

/hold cancel