pulsar (ticdc): add integration test for pulsar + ssl and oauth2

[asddongmen]

What problem does this PR solve?

Issue Number: ref #10602

What is changed and how it works?

1. Enable the Pulsar consumer to consume messages from a TLS and OAuth 2.0 enabled Pulsar server.
2. Include self-signed certificates and keys to enable Pulsar + SSL and OAuth 2.0 integration testing.
3. Ensure that the existing Pulsar sink integration test cases can be executed with SSL and OAuth 2.0 enabled.

Check List

Tests

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

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]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[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 asddongmen. 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