Connect Request Recorder Failures to Error Log

## Motivation

When resilience operations fail, these failures should be recorded to the error log for later analysis and correlation with audit logs.

- Resilience failures are logged but not persisted to error_logs table
- Cannot query historical resilience failures

## Required Features

- After request processing, check RequestRecorder for failures
- Create error log entries for each failure using ErrorLogService
- Include request_id, operation name, and error message
- Implement as middleware or hook in request lifecycle
- Only record final failures (not retried attempts that eventually succeeded)

## Impact

- `src/ai/backend/common/resilience/recorder/`
- `src/ai/backend/manager/server.py` or common middleware
- Integration with ErrorLogService

## Testing Scenarios

- Verify failed resilience operations create error log entries
- Verify successful operations do not create error log entries
- Verify error logs include correct request_id
- Verify retried-then-succeeded operations are not logged as errors

JIRA Issue: BA-3730