Align Stripe plan changes to first-of-month proration anchors

[Copilot]

This issue tracks billing modernization for plan upgrades, including Stripe-based usage/billing consistency and month-aligned plan transitions. This PR addresses the proration/alignment slice by ensuring plan changes are created/updated with explicit monthly billing anchor behavior in Stripe.

• Plan-change subscription behavior

  • Updated OrganizationController.ChangePlanAsync to set Stripe proration explicitly on plan changes:
    • ProrationBehavior = "create_prorations"
  • Applied to both:
    • new Stripe subscription creation
    • existing subscription update flows

• Month-aligned billing anchor

  • Added Stripe BillingCycleAnchorConfig for subscription creation paths to align billing to the first day of month at 00:00:00.

• Controller cleanup

  • Extracted shared billing anchor construction into a single helper to keep Stripe subscription option assembly consistent across paths.

• Focused coverage updates

  • Extended OrganizationControllerTests assertions to validate:
    • ProrationBehavior is set to create_prorations
    • billing cycle anchor config is set to day 1, time 00:00:00

var subscriptionOptions = new SubscriptionCreateOptions {
    Customer = customer.Id,
    Items = [new SubscriptionItemOptions { Price = model.PlanId }],
    BillingCycleAnchorConfig = CreateMonthlyBillingCycleAnchorConfig(),
    ProrationBehavior = "create_prorations"
};

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ niemyjski
❌ Copilot
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[niemyjski]

Follow-up reviewer-feedback and thermo-nuclear audit completed at head 0dec511f2cabc1658fb921ea3adca3b7538f92f8 against base dc940dd15c8d222d9764080622fdf4583d4546b8.

• Feedback inventory/classification: GraphQL review threads: 0; inline review comments: 0; submitted reviews: 0. There are no human, Codex, or Copilot reviewer findings to reply to or resolve. The coverage-bot comment is current verification evidence and non-actionable. The CLAassistant comment is current and external: the Copilot co-author has not signed. The PR body's old helper-name snippet is outdated by the current CreateMonthAlignedSubscriptionOptions consolidation; the described behavior remains accurate.
• RCA and surgical fix already on the live head: subscription-create branches assembled Stripe options independently and relied on implicit/default anchor/proration behavior. Commit 0dec511 centralizes the first-of-month UTC anchor and create_prorations policy for both creation paths; existing-subscription updates set create_prorations explicitly.
• Thermo-nuclear result: reviewed the complete two-file effective diff (66 insertions, 7 deletions). No remaining branch-caused correctness, compatibility, authorization, serialization, race, partial-update, type/boundary, duplication, spaghetti, needless orchestration, or non-atomicity finding was proven. The production handler is 963 lines (945 on base); the test file was already over 1,000 lines and moved from 1,962 to 2,003 without crossing the threshold in this PR. No API contract/snapshot change is involved.
• Verification: dotnet restore Exceptionless.slnx passed; dotnet build Exceptionless.slnx --no-restore --configuration Release -m:1 passed with 0 warnings/0 errors; the three focused plan-change tests each passed 1/1; git diff --check origin/main...HEAD passed; origin/main is an ancestor of head. Exact-head CI is green for version, test-api, test-client, test-e2e, and docker-build.

Verdict: code and CI are ready. The sole remaining external merge blocker is the pending Copilot contributor CLA.

[github-actions]

Package	Line Rate	Branch Rate	Complexity	Health
Exceptionless.Insulation	37%	35%	286	❌
Exceptionless.Core	75%	67%	9992	➖
Exceptionless.Web	85%	69%	7024	✔
Exceptionless.AppHost	38%	40%	139	❌
Summary	78% (23502 / 30296)	67% (11023 / 16516)	17441	✔

[niemyjski]

Final follow-up at head ce0c1dab3129fba781a304cdc3f180a5ed50e555 against current main d2dee90052d7ac229efc4777b719c8f7c3fe0f5b:

• Re-audited GraphQL review threads, REST inline comments, submitted reviews, and the PR conversation: 0 review threads, 0 inline comments, and 0 submitted reviews. There are no actionable reviewer findings to reply to or resolve; CLA and coverage comments are administrative/verification signals.
• Merge-forward commit ce0c1dab3 refreshed the branch without rebasing or changing the effective feature diff (still 2 files, 66 insertions, 7 deletions); git diff --check origin/main...HEAD passes.
• Local verification: restore passed; Release build passed with 0 warnings/0 errors; the new existing-customer-without-subscription regression passed 1/1. Two separate local invocations were blocked after the PR-specific assertions by shared Elasticsearch test-* index contention from concurrent worktrees; no code change was justified from those environment failures.
• Exact-head GitHub Actions run 31623005405 passed version, test-api (full API suite with coverage), test-client, test-e2e (including Aspire readiness and Playwright), and docker-build.

Code and CI are ready. The PR remains draft/mergeable; the only active blocking status is the external Copilot contributor CLA.