[PM-39432] chore: pass null Send repository in SdkRepositoryFactoryImpl

[adudek-bw]

🎟️ Tracking

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

📔 Objective

Paired with bitwarden/sdk-internal#1217, which adds a Send slot to the SDK's client-managed Repositories struct (via the create_client_managed_repositories! macro in bitwarden-pm/src/migrations.rs). The new field surfaces through the UniFFI Kotlin binding as a required send constructor parameter on com.bitwarden.sdk.Repositories.

This PR adds send = null to the call site in SdkRepositoryFactoryImpl so the Kotlin code compiles against the new SDK. No behavioral change — Android doesn't persist Sends locally today, so passing null matches the existing pattern used for folder, userKeyState, ephemeralPinEnvelopeState, and organizationSharedKey.

Without this paired change, the SDK PR's breaking-change detection job for Android fails with:

e: SdkRepositoryFactoryImpl.kt:37:13 No value passed for parameter 'send'.

When Android starts persisting Sends locally, this null can be replaced with a real SdkSendRepository implementation, similar to how cipher and localUserDataKeyState work today.

📸 Screenshots

N/A — no UI changes.

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

Reviewed the single-line addition of send = null to the Repositories(...) constructor call in SdkRepositoryFactoryImpl. The change aligns the Kotlin code with the paired SDK PR that adds a required send parameter, and it follows the established convention for other unpersisted repository slots in the same file (folder, userKeyState, ephemeralPinEnvelopeState, organizationSharedKey). No behavioral change, no security or correctness concerns.

Code Review Details

No findings. The change is a no-op compilation fix that matches the existing null-slot pattern, is well-documented in the PR description, and references PM-39432 along with the paired SDK PR.

[vvolkgang]

On hold until bitwarden/sdk-internal#1217 is merged.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (sdlc/sdk-update@795659d). Learn more about missing BASE report.

Additional details and impacted files

@@                Coverage Diff                 @@
##             sdlc/sdk-update    #7120   +/-   ##
==================================================
  Coverage                   ?   86.12%           
==================================================
  Files                      ?      885           
  Lines                      ?    64385           
  Branches                   ?     9580           
==================================================
  Hits                       ?    55449           
  Misses                     ?     5492           
  Partials                   ?     3444           

Flag	Coverage Δ
app-data	17.58% <100.00%> (?)
app-ui-auth-tools	18.76% <0.00%> (?)
app-ui-platform	16.49% <0.00%> (?)
app-ui-vault	27.52% <0.00%> (?)
authenticator	6.18% <0.00%> (?)
lib-core-network-bridge	4.03% <0.00%> (?)
lib-data-ui	1.13% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

[david-livefront]

Do we need to implement this any time soon?

[adudek-bw]

Not unless it's already on your roadmap :)