QA-2279: add OrganizationEventScene to the seeder

[awiester-bw]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/QA-2279

📔 Objective

The SeederApi can create organizations, members, collections, and groups, but has no way to create audit events. This blocks per-test seeding for the Events Public API test class, whose positive cases read events back from GET /public/events and need an org that already has some. This adds OrganizationEventScene, mirroring OrganizationGroupScene: it resolves the org, then writes Count audit-event rows (default 2) for it through IEventRepository, returning how many were seeded. The reflection-based scene registration picks it up automatically by class name.

It targets the self-host SQL event store ([dbo].[Event]), which is what qa-automation runs, and GET /public/events reads that same store there. The cloud Table Storage path (which needs EventTableEntity indexing) is out of scope and noted on the ticket. Verified by a passing build (0 warnings, warnings-as-errors on), dotnet format --verify-no-changes, and the pr-review-toolkit agent pass. No scene has a dedicated test harness in this repo (sibling scenes are untested), so no unit test was added, consistent with precedent.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.35%. Comparing base (42d286e) to head (8ef1a2f).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8175   +/-   ##
=======================================
  Coverage   63.35%   63.35%           
=======================================
  Files        2337     2337           
  Lines      101412   101412           
  Branches     9159     9159           
=======================================
+ Hits        64248    64249    +1     
+ Misses      34951    34950    -1     
  Partials     2213     2213           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.