[Question] do we need execute ever plugin in the same schduler when some of the plugins call publishOn to other scheduler?

### Question

We might call some external services from other scheduler, for example lettuce-redis library can publish reactor stream into lettuce-event-poll-xxx scheduler.

Below is a example from our service logging. We use `shenyu-worker` for default plugin execution scheduler, but we might use netty client `xxx-shenyu-netty` to call a external http api by some cases, and then the subsequence plugins are executed in the `wrong` scheduler .

Is there any way shenyu can check scheduler that we expected or keep every plugin execution in the same scheduler?
In our case, switch back to `shenyu-worker` after the customized plugin execution finished.

Start by tracing how shenyu-worker schedules plugin execution and how a custom plugin's publishOn handoff changes the scheduler, using the reported lettuce-event-poll-xxx and xxx-shenyu-netty cases. Determine the expected scheduler boundary and define done as a documented or tested behavior for subsequent plugins after the customized call finishes.

Written by the indexing model from the issue text.