Publish CI artifact with event log aggregations

[iduartgomez]

Our freenet_test macro sets up infrastructure so we can collect the different event logs aggregations. In case of failure it would be good to have access to the different files we write out for debugging.

Additionally (can separate into an other issue, although this should be an ongoing effort), we should keep improving the event collection so we can have enough traceability about what's happening on each peer and can recontruct transaction and connection history in a coherent source of truth.

[github-actions]

🤖 Auto-labeled

Applied labels:

• T-enhancement (95% confidence)
• E-medium (80% confidence)
• A-developer-xp (90% confidence)

Reasoning: The request is for improving CI/test infrastructure to publish event-log aggregation artifacts for debugging, which is an enhancement to existing developer tooling rather than a bug or new feature. Implementing CI artifact publishing is moderately scoped (requires CI config changes and test harness adjustments), so E-medium is appropriate. The change is primarily about developer experience/CI, so A-developer-xp is the relevant area.

Previous labels: none

If these labels are incorrect, please update them. This helps improve the auto-labeling system.