Users — Name can be set at creation and edited afterwards (API + SPA) #163

Parent issue

Reported during QA session.

What's wrong

A user's Name can never be set. The New user dialog on the Users screen only asks for Email, Password, and Role — no Name field, and the create endpoint does not accept one. There is also no edit flow afterwards, so every user created through the app shows "—" in the Users table's Name column forever.

What I expected

• When creating a user, I can enter their Name.
• An Admin (owner) can later edit a user's Name from the Users screen — to fix a typo, or fill in the blank Name on users created before this lands.

Steps to reproduce

1. Log in as Admin (owner) and open the Users screen.
2. Click "New user" — the dialog offers only Email, Password, and Role.
3. Create the user — the new row shows "—" in the Name column.
4. Look at any user row: the only action is the "flocks" link on Worker rows. No edit action exists, so the Name can never be changed.

Blocked by

None — can start immediately.

Additional context

Name is already a first-class field on the user: the Users table has a Name column, and the two seeded logins ("Administrator", "Worker") display theirs — they are the only users that ever get one. There is currently no user update flow of any kind (no edit screen, no update endpoint); the glossary deferred editing an existing user's role or password to a later slice, and Name fell into the same bucket. The edit half could share an "Edit user" dialog with #165 (admin password set), but each is independently shippable. Glossary/Help updates ride along.

(Absorbed #164, which covered the edit half separately.)