### Elasticsearch Version

main

### Installed Plugins

_No response_

### Java Version

_bundled_

### OS Version

n/a

### Problem Description

Similarly to the `_update` API (see issue description in https://github.com/elastic/elasticsearch/issues/102933) there can be a problem with `_schedule_now` API manifested by transform other than requested being triggered by the API call.

There were no customer requests related to this problem so far, possibly because this API is relatively new and not used that much in production. Moreover, the customer may not even realize that when they trigger `_schedule_now` for transform `A`, other transforms (`B`, `C` and so on) get triggered too.

### Steps to Reproduce

1. Spawn multiple transforms until at least 2 of them are assigned to the same node
2. Call `_schedule_now` on transform `A`
3. Observe how transform `B` assigned to the same node is also triggered

### Logs (if relevant)

_No response_
x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/transform/action/ScheduleNowTransformAction.java
public static final Response TRUE = new Response(true);
        private final boolean acknowledged;
        public Response(StreamInput in) throws IOException {
            super(in);
            acknowledged = in.readBoolean();
        }
        public Response(boolean acknowledged) {
            super(Collections.emptyList(), Collections.emptyList());
            this.acknowledged = acknowledged;
        }
        public Response(
            List<TaskOperationFailure> taskFailures,
            List<? extends ElasticsearchException> nodeFailures,
            boolean acknowledged
        ) {
            super(taskFailures, nodeFailures);
            this.acknowledged = acknowledged;
        }