Pangolin Blueprint Target Activation Bug

### Describe the Bug

## Summary

After applying a blueprint configuration via the Pangolin dashboard, resources return "Bad Gateway" until the target is manually deactivated and reactivated.

## Steps to Reproduce

1. Open Pangolin dashboard and navigate to **Settings > Blueprints**
2. Paste blueprint configuration (example below)
3. Click **Apply**
4. Access the service URL (e.g., `https://metube.example.com`)
5. **Result**: "Bad Gateway" error

## Workaround

1. Open Pangolin dashboard
2. Navigate to the affected resource (e.g., MeTube)
3. Go to **Targets** section
4. **Disable** the target entry
5. Click **Save** (may need to click multiple times for it to register)
6. **Re-enable** the target entry
7. Click **Save** again (may need to click multiple times)
8. Access the service URL
9. **Result**: Service works correctly

## Example Blueprint

```yaml
public-resources:
metube:
name: MeTube
protocol: http
full-domain: metube.example.com
ssl: true
auth:
sso-enabled: true
sso-roles:
- Family
targets:
- site: your-site-identifier
hostname: 10.96.0.152
port: 8081
method: http
```
## Additional Notes

- Reproducible issue - occurred at least 5 times across different services
- Toggle workaround consistently resolves the issue for me

### Environment

- **OS Type & Version**: Debian GNU/Linux 13 (trixie)
- **Pangolin Version**: 1.14.1
- **Gerbil Version**: 1.3.0
- **Traefik Version**: 3.6.4
- **Newt Version**: 1.5.0
- **Olm Version**: N/A
- **Deployment**: Self-hosted

### To Reproduce

1. Open Pangolin dashboard and navigate to **Settings > Blueprints**
2. Paste blueprint configuration (example below)
3. Click **Apply**
4. Access the service URL (e.g., `https://metube.example.com`)
5. **Result**: "Bad Gateway" error

### Expected Behavior

After applying a blueprint via the dashboard, targets should be immediately active and functional without manual intervention.