fix: migrate to v2/v3 GraphQL actions after direct-table removal

[blue4209211]

Summary

The server's actions.yaml removed almost all direct Hasura table APIs in favor of v2/v3 actions. This PR migrates nbctl off the removed APIs and then corrects the action shapes against the actual app code at nudgebee/nudgebee-enterprise/app.

Commit 1 — initial migration (f473dba)

Switched all direct-table calls to v2/v3 action equivalents:

• cloud_accounts* → get_cloud_accounts_v2
• users → admin_get_users_by_tenant_v2
• events → events_v2
• traces_by_pk / traces_v3 → traces_query
• llm_conversations* / llm_functions → llm_conversation_list_v2 / ai_get_conversation_v3 / llm_functions_v2
• update_cloud_accounts → cloud_account_update
• delete_llm_conversation_saveds_by_pk → ai_delete_saved_conversation

Commit 2 — schema corrections (9ef3a1a)

After cross-checking with the web app's actual gql calls, fixed several guess-driven mistakes:

• ai_get_conversation_v3: id/session_id/status live inside conversation { ... }, not top-level
• ai_delete_saved_conversation: input is {conversation_id} only
• cloud_account_update: variable is $object (not $input); response is {affected_rows} (not {id,status})
• events_v2: fields are account_id/resource_id (not cloud_account_id/cloud_resource_id)
• llm_conversation_list_v2: bookmark filter is is_saved (not is_bookmarked); username filter is user_username; order_by is array with enum
• Dropped updated_at from get_cloud_accounts_v2 (not in schema)

Also restored columns that didn't actually need separate calls:

• accounts list: agents/cloud_account_attrs jsonb on the row → Agents/Attributes count columns back
• admin users list/get: user_roles/user_groups/last_accessed_at on the row → Roles/Groups/Last Login columns back

Test plan

• go build ./... clean
• go test ./... passes (unit tests for accounts, admin users, events, traces, nubi all updated to new shapes)
• Manual smoke (recommended order — exercises riskiest changes first):
  • nbctl accounts list → nbctl accounts get <id> (cloud + k8s)
  • nbctl events get <id>
  • nbctl traces query → nbctl traces get <trace_id>
  • nbctl admin users list → nbctl admin users get --username <u>
  • nbctl accounts enable <id> / disable <id>
  • nbctl nubi — session, history, bookmarks
• Run with --verbose to capture GraphQL request/response in nbctl_graphql.log if anything fails

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request migrates multiple CLI commands to use a new set of versioned GraphQL APIs (v2/v3), which involve changes to query structures, response handling, and the introduction of new data fields. The updates affect account management, user administration, event retrieval, and trace querying. Key feedback includes a high-severity security concern regarding GraphQL injection in cmd/traces_get.go due to string interpolation of user input, and a usability regression in cmd/admin_users_get.go where user roles and groups are now printed as raw JSON instead of formatted strings.