[PM-36419] [BEEEP] Add collection management settings to seeder

[eliykat]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-36419

📔 Objective

Allow control of collection management settings via the seeder. These alter organization/collection behavior significantly and go hand-in-hand with different collection/group assignments to set up a customer's preferred access controls.

I wanted to avoid appending lots of nullable parameters to various methods, so I've created an OrganizationOverrides bucket to contain them. This should allow for easier modification in in the future as well.

📸 Screenshots

[eliykat]

Opinionated change I wanted to call out: it's correct that these are not plan-gated, however they all default to false in production, so omitting them here is a more sensible default. Particularly as we now have overrides you can apply to turn them on if you want. (I've included UseAutomaticUserConfirmation in the overrides as well for completeness.)

I assume nobody is relying on these default values yet but we can discuss if this is expected to cause impact anywhere.

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

Reviewed the seeder changes that introduce an OrganizationOverrides bucket for collection management settings (UseAutomaticUserConfirmation, AllowAdminAccessToAllCollectionItems, LimitItemDeletion, LimitCollectionCreation, LimitCollectionDeletion). The change wires overrides consistently through preset JSON, CLI args, OrganizationVaultOptions, the recipe builder, and CreateOrganizationStep. Plan-default seeding for these properties is removed so seeded organizations now match production defaults (false), as the author explicitly called out for discussion. Scope is limited to util/Seeder and util/SeederUtility — dev/test tooling only.

Code Review Details

No findings. The override pattern is internally consistent (schema, model, CLI, options, step), null-coalescing in ApplyOrganizationOverrides cleanly preserves plan defaults when overrides aren't set, and the schema descriptions correctly describe what true means without claiming a default. The behavior change in seed defaults is deliberate, called out in the author's self-review thread, and aligns with production behavior.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.62%. Comparing base (ea007b6) to head (d962be2).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7576      +/-   ##
==========================================
+ Coverage   59.61%   59.62%   +0.01%     
==========================================
  Files        2096     2096              
  Lines       92580    92580              
  Branches     8245     8245              
==========================================
+ Hits        55190    55200      +10     
+ Misses      35437    35427      -10     
  Partials     1953     1953              

☔ View full report in Codecov by Sentry.
📢 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.