[FND-180] Detach Workflows Editor from current bound to Tab controller

[klaustopher]

Ticket

https://community.openproject.org/wp/FND-180

[github-actions]

Warning

Flaky specs

• rspec ./modules/backlogs/spec/features/inbox_column_spec.rb[1:7:1]

🤖 Ask Copilot to investigate

Copy the prompt below into a new comment on this PR to delegate the investigation to GitHub Copilot. It will look into the flakiness and open a separate pull request with you as reviewer.

@copilot The following spec(s) are flaky in CI (first seen on PR #24477, linked for reference only):

- `rspec ./modules/backlogs/spec/features/inbox_column_spec.rb[1:7:1]`

Treat this as a standalone task, unrelated to PR #24477. Create a new branch from origin/dev and open a new pull request targeting dev — do not stack it on PR #24477 or reuse that branch.

Follow the playbook in docs/development/testing/handling-flaky-tests/README.md to find the root cause and fix the underlying race — do not skip, delete, or weaken the spec to make it pass; disabling is a last resort per the playbook, and only with a bug ticket. Verify the fix by running the spec(s) repeatedly (e.g. `script/bulk_run_rspec --run-count 10`).

If you cannot reproduce the flake or are not confident in a fix after reasonable investigation, do not fabricate a change or skip the spec to force CI green. Instead, leave the pull request in draft and document what you tried, the suspected cause, and any leads in its description, then assign @klaustopher to take over.

Once the fix is verified, title the PR after the spec(s) it fixes, and use the PR description to explain the root cause, how the change resolves it, and the before/after results. Label the PR `flaky-spec`, assign @klaustopher, and request a review from @klaustopher.
On every commit, set @klaustopher as the sole co-author with a `Co-authored-by:` trailer (use their GitHub no-reply email so it links to their account), so it is traceable who dispatched the fix.

[mrmir]

Before we spend more time reviewing/fixing, I guess it makes sense to run it by @oliverguenther. Wdyt? To avoid #24457 not going through the wizard exactly and having some weirdness with the workflows tabs controller having to return back to the wizard etc. This is a much bigger refactor to completely detach the workflows editor from where it is hosted, but is it worth it?

[oliverguenther]

@mrmir had a quick chat with Klaus on this and a code review and click through. I think it's a solid idea to move workflows into its own editing component, so we can more easily replace it later with e.g., a visual component

[mrmir]

Aah cool, y'all did that already. Will review properly then 👍🏽

[mrmir]

Works quite well overall. 👍🏽

What still needs to be touched is mainly cosmetic:

1. Looks like the base element size was changed, resulting in the last row being cut off:
   

2. I have no idea what happened to the left side "Current Status" label:

   

   vs.

   

[klaustopher]

Style issues are fixed @mrmir, it was simply not applying the stylesheet. And we needed to add a block display for the form so that the padding was correctly applied to make room for the save button

[mrmir]

🎉