### What happened?

## Bug Description

The `get_next_standardized_reset_time()` function in `litellm/litellm_core_utils/duration_parser.py` has a critical bug that causes incorrect budget reset time calculations when large duration values are specified in seconds, minutes, or hours. The bug affects `_handle_second_reset()`, `_handle_minute_reset()`, and `_handle_hour_reset()` functions.

## Problem

When calculating reset times for durations that span multiple days, these functions only add 1 day to the reset time regardless of how many days the duration actually spans. This causes budget resets to be scheduled far too early.

### Example Scenario

**Working correctly:** - `budget_duration: "365d"` → Correctly calculates reset time 365 days in the future

**Broken:** - `budget_duration: "31536000s"` (1 year in seconds) → Incorrectly calculates reset time ~1 day in the future instead of 365 days

## Root Cause

### In `_handle_second_reset()` (lines 318-364):

```python # Calculate next second aligned with the value # ... calculation logic ...

# Handle overnight case if next_hour >= 24: next_hour = next_hour % 24 next_day = base_midnight + timedelta(days=1) # BUG: Only ad…