User Status Management Issues for OOO and Idle States

Description

There are multiple issues in the user status lifecycle affecting OOO transitions, IDLE state accuracy, and 7-day idle tracking for Discord roles. These bugs cause users to get stuck in incorrect states or miss expected transitions entirely.

Current Behavior

1. Users remain stuck in OOO indefinitely

   • Users who return from OOO still appear as OOO.
   • No automatic transition back to ACTIVE or IDLE.

2. Users are marked IDLE during active OOO

   • Some users in OOO are incorrectly transitioned to IDLE before their OOO period ends.

3. 7-day idle tracking is broken

   • Users who should qualify for group-idle-7d+ never receive the role.
   • Idle duration is effectively always calculated as 0.

Expected Behavior

1. OOO should end automatically

   • When the OOO until time passes, users should transition correctly to:
     • ACTIVE (default), or
     • IDLE (if applicable based on activity)

2. OOO state should not be interrupted

   • Users must remain in OOO for the full duration defined by until.

3. Idle tracking should be accurate

   • When a user becomes IDLE, idleFrom must be set.
   • Users idle for 7+ days should correctly receive the Discord role.