Changed member welcome email job to run based on config

[tomerqodo]

Benchmark PR from qodo-benchmark#246

---

Note

Shifts welcome email gating from a labs flag to a config key and aligns outbox/job behavior and tests.

• Replaces labs.isSet('welcomeEmails') with config.get('memberWelcomeEmailTestInbox') in MemberRepository.create and the welcome email job scheduler
• Outbox MemberCreatedEvent now added when config is set or when source is member; skipped if config is unset or source is disallowed (import, admin, api)
• Schedules process-member-welcome-emails every 5 minutes only when the config key is present and not running tests
• Updates integration/unit tests to use configUtils and config.get stubs, asserting new conditions and payloads (timestamp, source)

^{Written by Cursor Bugbot for commit 96cac63. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Inverted condition prevents job from being scheduled

High Severity

The condition was changed from !hasScheduled.processOutbox to hasScheduled.processOutbox, inverting the logic. Since hasScheduled.processOutbox is initialized to false, the condition hasScheduled.processOutbox && ... is always false, so jobsService.addJob() is never called and the welcome email processing job is never scheduled.

 

[cursor]

Wrong operator breaks source filtering for outbox entries

High Severity

The condition was changed from && to ||, breaking source filtering. The original logic required BOTH the feature flag AND an allowed source. With ||, when welcomeEmailConfig is truthy, outbox entries are created for ALL member sources (including import, admin, api) instead of only the 'member' source, contradicting the test expectations.