`UpdateTask` resets controller status on reapply and accepts client-supplied status

[sauryagur]

UpdateTask saves the whole client-supplied Task, including status. A normal ax apply sends no status, so reapplying a running Task replaces its controller-written status with Pending and clears its conditions and other runtime fields.

The endpoint also accepts a status supplied by a client. In particular, the reconciler trusts WorkspaceReady=True and can skip the workspace readiness check.

[sauryagur]

Steps to reproduce

Using server.NewServer(memory.NewStore()), with no external services:

1. Create a Task through UpdateTask without status.
2. Set its status through UpdateTaskStatus to Running, with an ID and WorkspaceReady=True.
3. Call UpdateTask again with the same Task spec and no status. GetTask now returns Pending, with the controller-written fields cleared.
4. Call UpdateTask with status.phase=Running and WorkspaceReady=True. GetTask returns those client-supplied values.

A local in-memory reproduction produced:

reapply changed controller phase: got "Pending", want Running
API persisted client-supplied status: phase="Running" conditions=[type:"WorkspaceReady" status:"True"]