Workflow privilege is read from the owner’s access row instead of ownership #9150

What happened?

For datasets, models and computing units, the owner is now treated as WRITE wherever access is read (apache/texera#8890 · fix(resource, computing-unit)…). Workflows still take the owner’s privilege from their workflow_user_access row alone, in workflow search and the workflow access checks, instead of from workflow_of_user.

Workflow sharing already refuses to change or revoke the owner’s row, so this can’t be triggered through the app. But a row removed or changed any other way (a direct DB edit, a past bug) would leave the owner with read-only access, or hide the workflow from its owner.

Expected: the owner of a workflow is always treated as WRITE, matching datasets, models and computing units.

How to reproduce?

Remove or downgrade the owner’s row in workflow_user_access for one of their workflows.
As the owner, search for it or open it. It’s missing from their list, or shown read-only.

Version/Branch

1.4.0-incubating-SNAPSHOT (main)

Commit Hash (Optional)

No response

What browsers are you seeing the problem on?

No response

Relevant log output