Identify and implement five code reduction opportunities

Identify top 5 opportunities to massively reduce the amount of code (lines of code) in any part of the repo: - Similar functionality that can be unified and reused - Code that has been valuable but no more - A front end component or a group of them duplicate another component/page functionality. Use the most modern and nice looking - etc. Now implement them :)

Five code reductions shipped as PR #7727 (queued in the merge lane): jaahd test loop drivers/pane, 18 api seed wrappers inlined, tools test fixtures shared, db.every_org_session for three cron sweeps (guarded, pinned), web api-mock overriding helper. 49 files, net -188. Review lanes caught and reverted one bad deletion. Quick gate and lane stages green. No UI surface affected. Memory: used mem-32882; none proposed.