Disable start_from_trigger altogether for now

[uranusjr]

Close #54627. See in-code comments for details.

[ashb]

What do we have to do to re-enable it for 3.1 timeframe?

[uranusjr]

We need to figure out how to render the task template without spawning a worker (or at least be able to spawn a process that’s significantly more lightweight than a task worker) to make this worthwhile. Otherwise I feel we should just remove this feature altogether since it would not provide any benefits.

[github-actions]

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker 91e1029 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

[uranusjr]

Not going to backport per suggestion from @vatsrahul1001. This issue is not repro-able in 3.0.x.

[dabla]

We need to figure out how to render the task template without spawning a worker (or at least be able to spawn a process that’s significantly more lightweight than a task worker) to make this worthwhile. Otherwise I feel we should just remove this feature altogether since it would not provide any benefits.

I have a PR open for that, it's a pity this has been closed as my PR is ready to be merged.