test(mobile): use explicit expected values in isServer consistency test

[guesung]

Summary

• Replace relative assertions (toBe(secondCall)) with explicit expected values (toBe(false)) in isServer client-side consistency test
• Aligns with the pattern used in isServer.ssr.test.ts and getSafeAreaInset.ssr.test.ts

Test plan

• yarn test passes

[Copilot]

Pull request overview

Updates the isServer client-side consistency test to assert explicit expected values instead of comparing results across calls, aligning the test style with other SSR-related tests in the repo.

Changes:

• Replaced relative equality assertions (toBe(secondCall)) with explicit boolean expectations (toBe(false)) for isServer() repeated calls.

[kimyouknow]

LGTM!

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3369fa7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR