changefeed (ticdc): fix owner stuck when closing a changefeed (#6882)

[ti-chi-bot]

This is an automated cherry-pick of #6882

What problem does this PR solve?

Issue Number: close #6859

What is changed and how it works?

Use c.isReleased instead of c.initialized to determine whether we should release resources of a changefeed, otherwise if an error occurs in the middle of c.initialize(), the c.initialized will be false, so the resources of a changefeed would not be release expectantly, which leads to some goroutines leak and can not be cancel by c.cancel().

Check List

Tests

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

1. make build-failpoint
2. start cdc server
3. create a changefeed
4. error occur when changefeed initializing, and this changefeed will be closed immediately
   
5. cli changefeed [ pasue ,resume ,remove ] this changefeed, all commands work well which indicate the owner is working normally.

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]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-chi-bot]

@ti-chi-bot: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

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.