kafka: avoid create changefeed failures if can't get a topic from broker (#5696)

[ti-chi-bot]

This is an automated cherry-pick of #5696

What problem does this PR solve?

Issue Number: close #5563

What is changed and how it works?

If ticdc can't get the topic from kafka broker, still create a changefeed instead of throwing an error.

Check List

Tests

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

Target	Startup mode	changefeed create result	Query after create	Runtime write test	Notes
master	Default, old arch	Failed, exit code 1	ErrChangeFeedNotExists	Not reached	CreateTopicAndWaitUntilVisible treated the topic as unavailable and attempted CreateTopic; Kafka returned Topic authorization failure
Current branch	Default, old arch	Failed, exit code 1	ErrChangeFeedNotExists	Not reached	Same visible behavior after rebuilding bin/cdc from acl-0720 @ 6225925f; this run did not use the modified downstreamadapter implementation
Current branch	cdc server --newarch	Success, exit code 0	state: normal	state: warning, ErrKafkaSendMessage after DDL	This run exercised the modified downstreamadapter implementation; create passed by skipping topic creation after authorization failure, but runtime write still requires Topic Write

Questions

Will it cause performance regression or break compatibility?

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

Release note

Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

Summary by CodeRabbit

• Bug Fixes
  • Improved handling of Kafka authorization failures during topic discovery and creation.
  • Services can now continue using the configured partition count when topic administration is denied.
  • Topic partition information remains available for subsequent operations.
• Tests
  • Added coverage for authorization failures during topic metadata retrieval and topic creation.

[ti-chi-bot]

@wk989898 This PR has conflicts, I have hold it.
Please resolve them or ask others to resolve them, then comment /unhold to remove the hold label.

[ti-chi-bot]

@ti-chi-bot: ## If you want to know how to resolve it, please read the guide in TiDB Dev Guide.

Details

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 ti-community-infra/tichi repository.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 345fe379-df2f-4e6f-8f8c-828c60e9668d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[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 ask for approval from wk989898. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Details

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]

Cherry-pick conflicts appear resolved; removing the do-not-merge/hold label.

[wk989898]

Fixed by #5772

[ti-chi-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 LGTMed and approved by the reviewers firstly.
2. For pull requests to TiDB-x branches, it must have no failed tests.
3. AFTER it has lgtm and approved labels, please wait for the cherry-pick merging approval from triage owners.

Details

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-sigs/prow repository.