Make rake console run as a dynflow client to allow access to features provided by dynflow
- Fixes #30528 - Run rake console as dynflow client
Dynflow identifies separate runtime units (think processes) as worlds. Dynflow
distinguishes two kinds of worlds, executors worlds which can actually perform
things and client worlds, which can only ask the executor worlds to execute
something on their behalf.
Due to the recent move to sidekiq and puma, Dynflow gets initialized slightly
differently and all rake tasks now don't register themselves as Dynflow worlds.
This is mostly fine, since the world registration isn't exactly free operation
and most of the rake tasks don't interact with Dynflow in any way. However,
tasks which need to interact with Dynflow started failing. To fix this, we
introduced the dynflow:client rake task in 4e53859, on which other tasks can
depend and which registers the current process as a Dynflow client.
This patch allows running rails console as a Dynflow client so users can
interact with Dynflow from the console.