Make Print-Finished and Idle Lighting Timeouts Configurable

## Feature request

Please make the **Panda Status lighting timeouts configurable**, rather than having fixed delays.

There appear to be two separate timing stages that would benefit from configuration:

### 1. Print finished → Idle

After a print finishes, there is currently a period before the printer is considered **idle**.

It would be useful to make this delay configurable, for example:

* 30 seconds
* 1 minute
* 5 minutes
* 10 minutes
* 30 minutes

### 2. Idle → Lights Off

Once the printer is idle, the lights currently remain on for approximately **120 minutes (2 hours)** before automatically turning off.

This should also be configurable, for example:

* Disabled
* 5 minutes
* 10 minutes
* 30 minutes
* 60 minutes
* 120 minutes

### Desired behavior

Ideally, both timers would be exposed as independent settings:

```text
Print finished → Idle: [ 30 minutes ]
Idle → Lights off: [ 30 minutes ]
```

This would allow users to choose how long the printer should remain in its "finished" state and separately control how long the lighting should remain on once the printer has become idle.

### Example

With both values set to 30 minutes:

```text
Print finishes
↓
30 minutes
↓
Printer enters idle state
↓
30 minutes
↓
Lights turn off
```

The two timers should remain independent so users can have a longer finished-state period while still controlling when the lights turn off after the printer becomes idle.

### Why

The current fixed timing is not ideal for every setup. In particular, a **120-minute idle-to-lights-off delay is quite long** for users who want the lighting to shut off sooner after the printer has stopped being used.

Making both delays configurable would preserve the current defaults while giving users much more control over the lighting behavior.

No files, tests, or entry points are named. Start by finding the code handling the print-finished-to-idle transition and the approximately 120-minute idle-to-lights-off timer, then trace where settings are defined and persisted. Done means two independent settings exist, current defaults remain unchanged, and each timer follows its selected value, including disabled lights-off behavior.

Written by the indexing model from the issue text.