[CONSIDER] Custom alternative to docker-logs

## Context

Using third-party action for dumping Docker logs on CI failure in aRustyDev/timesketch.

## Third-Party Action Chosen

- **Repository:** `jwalton/gh-docker-logs@v2`
- **Version:** v2
- **Purpose:** Dump all docker container logs when workflow fails
- **Stars:** ~150
- **Last updated:** 2024

### Why Third-Party

- Simple, focused functionality
- Well-maintained
- No alternatives with more features needed

## Alternatives Evaluated

| Action | Repository | Pros | Cons |
|--------|------------|------|------|
| Manual docker logs | N/A | No dependency | Verbose workflow code |
| jwalton/gh-docker-logs | `jwalton/gh-docker-logs` | Simple, focused | Third-party |

## Currently Used In

| Repository | Workflow | Purpose |
|------------|----------|---------|
| `aRustyDev/timesketch` | `e2e-tests.yml` | Dump logs on e2e test failure |

## Build Custom If

- [ ] Third-party becomes unmaintained (no commits 6+ months)
- [ ] Need custom formatting or filtering
- [ ] Want to integrate with other logging services

## Notes

Low priority - current action works well. Deferred for future review.

Inizia esaminando e2e-tests.yml e il modo in cui jwalton/gh-docker-logs@v2 viene utilizzato per i test end-to-end falliti. La issue non definisce formattazione personalizzata, filtraggio, integrazioni o un ambito di sostituzione, quindi chiarisci questi requisiti prima dell’implementazione; i criteri di completamento non sono attualmente specificati.

Scritto dal modello di indicizzazione a partire dal testo della issue.