fix: pass user attributes during loginUserWithUserAttributes on Android

[imSzukala]

Why?

Fixes:

• https://github.com/intercom/intercom/issues/466832

loginUserWithUserAttributes on Android was silently dropping all user attributes (e.g. name, customAttributes) except email and userId. The Registration object was built from the params but withUserAttributes() was never called, so only the identity fields reached Intercom's backend.

How?

Call IntercomHelpers.buildUserAttributes(params) and attach the result via registration.withUserAttributes(userAttributes) before passing the registration to loginIdentifiedUser. The fix is applied to both the newarch and oldarch Android modules. The TypeScript type signature is also widened from Pick<UserAttributes, 'email' | 'userId'> to UserAttributes & ({ email: string } | { userId: string }) so callers can pass the full set of attributes.

Implementation Plan

Push commit and open PR against master

Context

Commit 132d0d1 on branch irena/user-attributes fixes a bug where Android was silently dropping all user attributes except email and userId during loginUserWithUserAttributes. The branch has no remote tracking yet.

Steps

1. Discard local unstaged changes in examples/example/src/App.tsx (revert to HEAD)
2. Push irena/user-attributes to origin with -u flag
3. Create PR against master using gh pr create
   • Title: fix: pass user attributes during loginUserWithUserAttributes on Android
   • Body: summary of the Android fix (newarch + oldarch modules, type signature update)

_{Generated with Claude Code}

[imSzukala]

Addressed the review feedback — simplified the loginUserWithUserAttributes type from UserAttributes & ({ email: string } | { userId: string }) to just UserAttributes.

The native layer already validates that at least one identifier (email or userId) is present at runtime, so the compile-time union type was adding complexity without meaningful safety benefit.