|WARNING| test/bpf_validate: use unit_test_suite_runner

[dpdklab at iol.unh.edu]

Test-Label: ai-code-review
Test-Status: WARNING
https://dpdk.org/patch/166545

_AI Code Review_

=== Patch Review: series.patch (via Claude) ===
Review date: 2026-07-03

# DPDK Patch Review

## Summary
This patch converts individual BPF validation tests from separate `REGISTER_ATTIC_TEST` entries to a single consolidated test using the `unit_test_suite_runner` infrastructure. The conversion is straightforward and follows DPDK test framework best practices.

## Findings

### Errors
None found.

### Warnings
None found.

### Info

**Test suite structure follows best practices**
The patch correctly uses `unit_test_suite_runner` with `TEST_CASE` macros and `REGISTER_FAST_TEST`. This is the preferred pattern for functional test infrastructure per AGENTS.md guidelines. The conversion from individual test registrations to a single suite is appropriate for the stated goal of reducing tmpfs usage.

**Net reduction in test framework overhead**
Consolidating 29 individual test registrations into a single suite runner reduces the per-test initialization and teardown overhead, which aligns with the stated motivation (CI tmpfs space constraints).

---

## Conclusion
The patch is clean and follows DPDK coding standards and test infrastructure guidelines. No correctness issues, style violations, or API concerns were identified. The conversion to `unit_test_suite_runner` is properly implemented and achieves the stated goal.