ticdc : http & https support in pulsar schema for changefeed.

[SandeepPadhi]

What problem does this PR solve?

Added support for HTTP and HTTPS schema for pulsar downstream. Currently, only pulsar and pulsar+ssl support is there. Issue: Issue Number: 11336 Ref: https://github.com/pingcap/tiflow/issues/11336

What is changed and how it works?

-> In addition to pulsar and pulsar+ssl schema types in pulsar changefeed creation , users will now will able to create changefeeds with HTTP and HTTPS type as broker schema for pulsar client.

Clients have to use:

1. pulsar+http -> for creating pulsar changefeed with HTTP endpoint
2. pulsar+https -> for creating pulsar chnagefeed with HTTPS endpoint.

Tests

1. Unit test
2. Feature test by deploying the image on k8s environment and creating multiple changefeeds.

Questions

Will it cause performance regression or break compatibility?

-> It should not cause any performance regression or break compatibility. It only addition schema addition for pulsar client creation.

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

-> Currently, documentation for pulsar downstream is not available on official document.

[ti-chi-bot[bot]]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[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 zhaoxinyu 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/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[sre-bot]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

:white_check_mark: SandeepPadhi
:x: Sandeep Padhi

---

Sandeep Padhi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ti-chi-bot[bot]]

Welcome @SandeepPadhi!

It looks like this is your first PR to pingcap/tiflow 🎉.

I'm the bot to help you request reviewers, add labels and more, See available commands.

We want to make sure your contribution gets all the attention it needs!



Thank you, and welcome to pingcap/tiflow. :smiley:

[ti-chi-bot[bot]]

Hi @SandeepPadhi. Thanks for your PR.

I'm waiting for a pingcap 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](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.

[ti-chi-bot[bot]]

[FORMAT CHECKER NOTIFICATION]

Notice: To remove the do-not-merge/needs-linked-issue label, please provide the linked issue number on one line in the PR body, for example: Issue Number: close #123 or Issue Number: ref #456.

_{:open_book: For more info, you can check the "Contribute Code" section in the development guide.}