feat: allow customize pulsar subscription name

[tabVersion]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

resolve #18377

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[xxchan]

Is actor_id needed?

[tabVersion]

we use exclusive subscription here, which mean a partition can only be consumed by one subscription. So actor-id is essential to avoid collision.

[xxchan]

1 pulsar split corresponds to 1 topic. In one source (i.e., one fragment), each actor will be assigned to different topics. So actor_id is not necessary. There's no collision.

[tabVersion]

1 pulsar split corresponds to 1 topic. In one source (i.e., one fragment), each actor will be assigned to different topics.

I dont get the logic

[xxchan]

The assignment looks like this. Where's the collision? Correct me if I'm wrong

• fragment 6 (topic t)
  • actor 1001 - topic t-partition-1, subscription rw-consumer-6
  • actor 1002 - topic t-partition-2, subscription rw-consumer-6
  • actor 1003 - topic t-partition-3, subscription rw-consumer-6
  • ...

[tabVersion]

I am afraid things not work in this way

The exclusive type is a subscription type that only allows a single consumer to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs. Note that if the topic is partitioned, all partitions will be consumed by the single consumer allowed to be connected to the subscription. source

We cannot attach multiple consumers to one subscription in exclusive mode. Since we want to manage the data parallelism, ie. partitions, in RisingWave, we have to separate the consumers from each parallelism into different subscriptions.

[xxchan]

I believe each subscription belongs to a different (sub)topic... They are not "one subscription"

[xxchan]

In the example above, rw-consumer-6 are 3 different subscriptions

[xxchan]

We already separated the consumers by subscribing to different sub topics. It's not by separate them into different subscriptions..