fix: suppress alerts for expected billing errors in increment-usage task

[ThyMinimalDev]

What does this PR do?

Suppresses trigger.dev alerts for expected billing errors in the increment-usage task. These errors are expected in certain scenarios and should not trigger alerts:

1. Temp/sandbox subscriptions: Errors like No such subscription: 'sub_temp_scale_but_should_be_per_user' where the subscription ID contains "temp" or "sandbox"
2. Non-usage-based subscriptions: Errors like Stripe subscription (sub_xxx) is not usage based - this task only handles usage-based subscriptions

When these expected errors occur, the task now logs at info level and returns successfully instead of throwing and triggering alerts.

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A - no documentation changes needed.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

1. Trigger the increment-usage task with a subscription ID containing "temp" or "sandbox"
2. Trigger the task for a subscription that is not usage-based
3. Verify that in both cases:
   • The task completes successfully (no retry/alert)
   • An info-level log is recorded with the error message
4. Verify that other errors still throw and trigger alerts as expected

Human Review Checklist

• Verify the error message patterns ("no such subscription", "is not usage based") match actual Stripe/service error messages
• Consider if string matching on error messages is robust enough for production
• Note: No unit tests added for isExpectedBillingError function

---

Link to Devin run: https://app.devin.ai/sessions/4d9b334d74e14d929451b173847004e9
Requested by: @ThyMinimalDev

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[cubic-dev-ai]

No issues found across 1 file