feat(server): add project metadata update API

[mattrobrob]

Issue for this PR

Closes #42906

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

Adds PATCH /api/project/:projectID for updating project names, icons, and startup commands.

Omitted fields are preserved, empty strings clear values, and unknown projects return a typed 404. Successful changes publish the complete project.updated event through the current server event stream. Generated clients and API references are updated, but client UI integration is intentionally out of scope.

This builds on the earlier work in #38443 and adapts it to the current project/worktree and event architecture.

How did you verify your code works?

• Full pre-push typecheck: 33 tasks passed across 39 packages.
• Core project tests: 18 passed, 1 skipped.
• Server test suite: 25 passed.
• Schema and Protocol tests, Client typecheck, generated documentation checks, targeted lint, and git diff --check passed.

Screenshots / recordings

Not applicable; this is an API and persistence change.

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

[github-actions]

Hey! Your PR title Project metadata api doesn't follow conventional commit format.

Please update it to start with one of:

• feat: or feat(scope): new feature
• fix: or fix(scope): bug fix
• docs: or docs(scope): documentation changes
• chore: or chore(scope): maintenance tasks
• refactor: or refactor(scope): code refactoring
• test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Based on my search, I found one potentially related PR:

Potential Related PR:

• feat(project): support project metadata updates (PR feat(project): support project metadata updates #38443)
  • feat(project): support project metadata updates #38443

This PR appears to be related as it deals with project metadata functionality. It may be addressing similar concerns or could share overlapping scope with the new "Project metadata api" PR #42904.

You may want to review PR #38443 to check if there's any overlap in functionality or if it was a previous attempt at implementing similar features.

[github-actions]

Thanks for updating your PR! It now meets our contributing guidelines. 👍