fix resign owner api not processed by owner node bug (#11770)

[ti-chi-bot]

This is an automated cherry-pick of #11770

What problem does this PR solve?

Issue Number: close #11769

What is changed and how it works?

/api/v2/owner/resign forward to owner node

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Questions

Will it cause performance regression or break compatibility?

Do you need to update user documentation, design documentation or monitoring documentation?

Release note

 `None`.

[ti-chi-bot[bot]]

This cherry pick PR is for a release branch and has not yet been approved by triage owners. Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be approved by the approvers firstly.
2. AFTER it has been approved by approvers, please wait for the cherry-pick merging approval from triage owners.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

[ti-chi-bot[bot]]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign suzaku for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/pingcap/tiflow/blob/release-7.5/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[ti-chi-bot[bot]]

@ti-chi-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
jenkins-ticdc/verify	256beffee8068fa5ea4e6df2319a54a54441b61d	link	true	/test verify
pull-cdc-integration-kafka-test	256beffee8068fa5ea4e6df2319a54a54441b61d	link	true	/test cdc-integration-kafka-test
pull-cdc-integration-pulsar-test	256beffee8068fa5ea4e6df2319a54a54441b61d	link	true	/test cdc-integration-pulsar-test
pull-cdc-integration-storage-test	256beffee8068fa5ea4e6df2319a54a54441b61d	link	true	/test cdc-integration-storage-test
pull-cdc-integration-mysql-test	256beffee8068fa5ea4e6df2319a54a54441b61d	link	true	/test cdc-integration-mysql-test

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).