Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

test(db): add regression test for twoFa-only duplicate detection in census validation

Before the fix, CheckGroupMembersFields skipped the duplicate-detection
block entirely when authFields was empty, even when twoFaFields contained
the only identity fields (e.g. email+phone for a CSP census). All members
passed validation as valid, and the failure only surfaced much later as
E11000 duplicate-key errors during the census participant bulk-write.

The test creates three members: two sharing the same phone number (phone
uniqueness is not enforced by the orgMembers index, making same-phone
members a realistic data state) and one with a unique phone. It then calls
CheckGroupMembersFields with authFields=[] and twoFaFields=[phone] and
asserts that:
  - both same-phone members appear in Duplicates
  - neither the second-seen duplicate nor the unique member is
    misclassified
  - MissingData is empty

This test would have failed against the unfixed code and passes with the
one-line guard change (len(authFields) > 0 || len(twoFaFields) > 0).

refs #434