## Bug Description

`LiteLLM_SpendLogs` uses the provider's response `id` field as the primary key (`request_id`). Ollama Cloud returns globally sequential IDs like `chatcmpl-213`, `chatcmpl-808`, etc. — these are shared across all users and models on Ollama's infrastructure, so they collide with previously logged requests. The INSERT silently fails on the PK constraint and the spend log is never written.

This means **all Ollama Cloud requests are invisible** in the spend logs / request log UI once the sequential counter wraps around or reuses an ID that was already recorded from a different model or session.

## Steps to Reproduce

1. Configure an Ollama Cloud model (`api_base: https://ollama.com/v1`) as an `openai/` provider 2. Send a few requests — they may or may not log depending on whether the returned `chatcmpl-NNN` ID already exists in the table 3. Query `LiteLLM_SpendLogs` — the Ollama requests are missing 4. Enable `LITELLM_LOG=DEBUG` — you can see `db_spend_update_writer.py:723 - Writing spend log to db` fires, but the row never appears

## Root Cause

`get_spend_logs_id()` in `spend_tracking_utils.py` prefers `response_obj.get("id")` over `kwargs.get("litellm_call_id")…