### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate

### What happened?

Replicate runtime pricing mixes seconds and milliseconds on current `litellm_internal_staging` at commit `65ca095d4d15a82372e53a547a2390a69f7e1797`

[`completion_cost`](https://github.com/BerriAI/litellm/blob/65ca095d4d15a82372e53a547a2390a69f7e1797/litellm/cost_calculator.py#L1110-L1150) documents `total_time` as the request duration in seconds

[`get_replicate_completion_pricing`](https://github.com/BerriAI/litellm/blob/65ca095d4d15a82372e53a547a2390a69f7e1797/litellm/cost_calculator.py#L696-L707) always divides the supplied duration by 1000:

```python return a100_80gb_price_per_second_public * total_time / 1000 ```

This conversion is correct when `completion_cost` sourced `total_time` from `_response_ms`

It is incorrect when a caller follows the documented API and passes seconds, and it is also incorrect when the helper derives `end_time - start_time`, which is a wall-clock duration in seconds

Those second-based paths undercount Replicate runtime cost by 1000 times

### Steps to Reproduce

Run:

```python from litellm.constants import DEF…