[PM-35830] Add ChangeEmailCommand

[ike-kottlowski]

🎟️ Tracking

PM-35830

📔 Objective

Introduces a new ChangeEmailCommand that encapsulates the user email change flow.

• Adds IChangeEmailCommand / ChangeEmailCommand under Bit.Core.Auth.UserFeatures.UserEmail, including claimed-domain enforcement, duplicate-email rejection, Stripe customer email sync with rollback on failure, and post-change push notifications (logout vs. settings sync depending on whether the user has a master password).
• Adds ChangeEmailCommandTests covering claimed-domain enforcement, disabled claiming orgs, duplicate email, same-user email, Stripe sync, Stripe rollback, and push branching.

This PR introduces the command only; switching callers from UserService.ChangeEmailAsync to the new command will follow in a separate PR.

Introduces a Admin Console Query to check if the email domain is allowed to be used.

[codecov]

Codecov Report

❌ Patch coverage is 98.07692% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 60.59%. Comparing base (8bd4af7) to head (e453bf2).
⚠️ Report is 14 commits behind head on main.

Files with missing lines	Patch %	Lines
.../Auth/UserFeatures/UserEmail/ChangeEmailCommand.cs	97.43%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7650      +/-   ##
==========================================
- Coverage   64.90%   60.59%   -4.32%     
==========================================
  Files        2141     2145       +4     
  Lines       94654    94957     +303     
  Branches     8456     8498      +42     
==========================================
- Hits        61435    57537    -3898     
- Misses      31118    35401    +4283     
+ Partials     2101     2019      -82     

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

[eliykat]

Letting @jrmccannon handle this one as he's discussed the approach with you already.

[ike-kottlowski]

@claude please review this PR.

[jrmccannon]

Thanks for adding the additional domain checks!

#7650 (comment)

[JaredSnider-Bitwarden]

Looking really good so far. Just some clarity work to be done:

[ike-kottlowski]

@claude please review my current changes. Please consider @JaredSnider-Bitwarden comments when responding.

[ike-kottlowski]

@claude Please review again. for gap 1 the user.BillingEmailAddress != null check is required to satisfy the nullable constraint for C# otherwise there is an error. It's defensive but fine. There is an additional test for the domain case matching, gap 4. We've also removed the throw when a gateway has a value but the customerId is null.

[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

[JaredSnider-Bitwarden]

Excellent work! LGTM! Please see my one comment below about QA note implications 👇

[JaredSnider-Bitwarden]

🏅 The stripe logic change to allow free users with a gateway but no customer id to change their email appears to be a good one, but please be sure we note it as a QA test case if it can be tested since it is a behavior change.

[ike-kottlowski]

I'll add it to the self-service ticket. These changes won't be able to be tested until AC has their email change flow implemented. These changes are foundational and not functional at this point in time.