[TASK] Support latest changes to start/stop API

[andyatmiami]

Certification

• I certify I am an Epic Owner for Kubeflow Notebooks 2.0 and expected to create planning-related issues.

Description

🛑 Blocked by #340

As part of the code review for #340 - the implementation of the API has changed:

• There is now a single API: POST /api/v1/workspaces/{namespace}/{name}/actions/pause

• This new (singular) API expects a request payload to indicate whether the intent is to start or pause the referenced workspace

  { 
    "data": {
      "paused": <bool> 
    }
  }
  

• The response payload is also slightly different:

  { 
    "data": {
      "paused": <bool> 
    }
  }
  

Acceptance Criteria

• Choosing Stop from the More Actions button on a Running Workspace in the Workspace List table should result in the Workspace entering the Paused state
• Choosing Start from the More Actions button on a Paused Workspace in the Workspace List table should result in the Workspace entering the Running state

[andyatmiami]

/area v2
/area frontend

[caponetto]

/assign

[caponetto]

/close

[google-oss-prow]

@caponetto: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.