Feat: adds interactive-session pause

[l-mansouri]

Overview

This PR implements the cloudos interactive-session pause command

JIRA

https://lifebit.atlassian.net/browse/LP-105730

Changes

• Implements the pause command
• Refactors documentation

Acceptance Criteria

Please add here as many scenarios as in the Story

Normally this acceptance criteria is tested in ADAPT workspace in PROD

Scenario 1: Successfully pause a running IA session

#### Jupyter #### vscode

Rstudio

spark

check status

Scenario 2: Attempt to pause an already paused session

Scenario 3: Force pause a session

Scenario 4: Attempt to pause a session with a non-existent session ID

[sentry]

Bug: The pause_session command with --wait passes incorrectly structured data to format_stop_success_output, causing the success message to display incorrect session details.
_{Severity: MEDIUM}

Suggested Fix

Update format_stop_success_output to handle the transformed data structure, using the keys id, cost, and runtime. Alternatively, pass the raw, untransformed API response to format_stop_success_output within the pause_session function.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: cloudos_cli/interactive_session/cli.py#L964-L966

Potential issue: When the `cloudos interactive-session pause --wait` command is used,
the `pause_session` function passes transformed data to the `format_stop_success_output`
function. However, `format_stop_success_output` expects raw API response data. It
attempts to access keys like `_id`, `totalCostInUsd`, and `totalRunningTimeInSeconds`,
but the transformed data contains `id`, `cost`, and `runtime` instead. This mismatch
causes the success message to display incorrect information, showing the Session ID as
"Unknown", Total Cost as "$0.00", and an incorrect runtime.

_{Did we get this right? 👍 / 👎 to inform future reviews.}