## System details
Omarchy v3.0.1 (Linux 6.16.8-arch3-1), manual installation over arch, running the scripts from cloned repo


## Problem Description

Waybar clock `:L` locale operator not respecting system timezone without TZ environment variable

In some manual installations, the waybar clock format `{:L%A %H:%M}` displays UTC time instead of the configured system timezone, even when `timedatectl` shows the correct timezone is set.

## Root Cause

The `:L` locale operator in waybar relies on the `TZ` environment variable to determine the timezone. While `timedatectl` can show and set the system timezone correctly, applications launched through certain desktop environments or window managers may not inherit the `TZ` environment variable, causing them to default to UTC.

## Example

- System timezone: `timedatectl show -p Timezone --value` returns `America/Argentina/Tucuman`
- Waybar config: `"format": "{:L%A %H:%M}"`
- **Without TZ:** Clock shows UTC time
- **With TZ:** Clock shows correct local time

## Current Workaround

Users have to hardcode the timezone in waybar config:
```json
{
    "clock": {
        "timezone": "America/Argentina/Tucuman",
        "format": "{:%A %H:%M}"
    }
}
```

## Proposed Solution

Set the `TZ` environment variable dynamically in omarchy's default bash environment:

```bash
# In default/bash/envs
export TZ="$(timedatectl show -p Timezone --value)"
```

This ensures:
1. **Dynamic detection:** Works for all users worldwide without hardcoding
2. **Proper inheritance:** Applications launched from terminals get the correct TZ
3. **Waybar compatibility:** The `:L` locale operator works as expected
4. **System consistency:** Matches the timezone configured via `timedatectl`