owner(ticdc): do not resign owner when ErrNotOwner is encountered (#9396)

[ti-chi-bot]

This is an automated cherry-pick of #9396

What problem does this PR solve?

Issue Number: close #9344

What is changed and how it works?

1. Do not resign owner when ErrNotOwner is encountered
2. Close processorManager as soon as possible

Check List

Tests

• Unit test
• Integration test

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]

[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 gmhdbjd for approval. For more information see the Kubernetes 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

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]

@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	7ce8d2d	link	true	/test verify
pull-dm-integration-test	7ce8d2d	link	true	/test dm-integration-test
pull-cdc-integration-mysql-test	7ce8d2d	link	true	/test cdc-integration-mysql-test
pull-cdc-integration-kafka-test	7ce8d2d	link	true	/test cdc-integration-kafka-test
pull-dm-compatibility-test	7ce8d2d	link	true	/test dm-compatibility-test

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.