Fix bug when connecting to a sandbox with a longer timeout

[jakubno]

Note

Adds extend_only to sandbox timeout to control TTL extension vs reset, updates orchestrator/handlers accordingly, deprecates refresh endpoint, and adds integration tests.

• API:
  • POST /sandboxes/{sandboxID}/timeout: add extend_only (default false) to control extending vs setting a new TTL.
  • POST /sandboxes/{sandboxID}/refreshes: marked as deprecated.
  • OpenAPI spec and generated code (spec.gen.go, types.gen.go, test models) updated.
• Backend:
  • Rename/repurpose KeepAliveFor param to extendOnly and enforce non-shortening when true.
  • Refresh handler now calls KeepAliveFor(..., extendOnly=true).
  • Timeout handler reads extend_only and passes through.
• Tests:
  • Add integration tests covering extend, no-shortening when extend_only=true, shortening when false/omitted, and not-found case.

^{Written by Cursor Bugbot for commit 9224e82. This will update automatically on new commits. Configure here.}

[linear]

ENG-3232 Fix bug when connecting to a sandbox with longer timeout - API part

[jakubno]

renamed it here to keep it consistent with API. I wanted to add a parameter which is description + default false

[dobrac]

whats the difference between set timeout extend_only=True and refresh?

[jakubno]

whats the difference between set timeout extend_only=True and refresh?

none, but refresh is deprecated

Also in SDK you probably don't want to do if (extend_only==True) {refresh()} else {setTimeout()}