[PERF] Add benchmark suite for concurrent scans and report generation

[utksh1]

Problem

SecuScan needs a production-grade improvement in this area: Performance baselines..

Scope

Create repeatable benchmarks for concurrent task starts, parser throughput, DB reads, and report exports, with regression thresholds.

Acceptance Criteria

• The implementation is focused and does not introduce unrelated UI, docs, lockfile, or formatting churn.
• Security-sensitive behavior has explicit negative tests where applicable.
• Existing tests continue to pass, and new tests cover the main success and failure paths.
• Documentation or configuration examples are updated when operator behavior changes.

Verification

CI or a scheduled workflow should publish benchmark artifacts and flag major regressions.

Difficulty

Hard, useful issue intended for experienced contributors.

[divyansha12]

Hey @utksh1, GSSoC '26 contributor here, would love to be assigned this!
So basically right now SecuScan has no way to know if a code change slowed things down — there's no baseline to compare against. This issue wants repeatable numbers across the four core areas so CI can actually catch when something regresses.
The tricky part is making those numbers trustworthy across runs. My plan is to isolate each benchmark at the I/O boundary so timings reflect actual logic not environment flakiness and set thresholds per area since parser throughput and report exports have very different latency profiles — a shared threshold would just hide real regressions. CI side I'd publish artifacts per run so you get trend diffs over time not just a pass/fail gate.
Can you assign this to me?