Update a project's name, or re-parent it into a folder.

EDITOR is enough to rename. RE-PARENTING is not a rename: a CONTAINMENT edge propagates the destination folder's level UNCHANGED (permissions/adapters/edges.py) and folder creation formerly had no role gate, so "EDITOR on the project" alone let any member create a folder they auto-ADMIN, move a project they merely edit into it, and come out ADMIN on the project — and therefore on every database under it, whose row policies then vanish (row_policy.py's admin_db_ids bypass), plus grant/revoke rights and the power to revoke the previous parent's grantees.

So a move requires ADMIN on the project and EDITOR on the destination folder — the same pair PATCH /files/{id}/move and PATCH /folders/{id}/move require. folder_id: null (move to root) still needs ADMIN on the project: it strips whatever the old parent conferred on everyone else.