fix(android): isRealDevice returns false on emulators - #11575

PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/tools/notes/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for.
• You have signed the CLA.
• All existing tests are passing.
• Tests for the changes are included.

What is the current behavior?

On Android, Utils.isRealDevice() gives the wrong answer. It returns true when Build.FINGERPRINT contains generic or vbox, which means it reports emulators as real devices and devices as not real. Current Android Emulator images also have fingerprints without generic (for example google/sdk_gphone64_arm64/emu64a:...), so a simple negation would still miss them. The iOS implementation is already correct.

What is the new behavior?

isRealDevice() returns false on the Android Emulator and on Genymotion, and true everywhere else. It detects emulators by:

• Build.HARDWARE being goldfish or ranchu (the emulator's virtual boards), or
• Build.FINGERPRINT starting with generic or containing vbox.

Nothing in core calls this on Android. Apps that worked around the inverted value will see it flip, so this should be called out in the release notes.

New unit tests in utils/native-helper-for-android.spec.ts cover a physical device, current and older emulator images, Genymotion, and missing build fields.

This makes the API match its documented contract, so the separate isSimulatorOrEmulator proposal in #9065 shouldn't be needed.

Closes #9064.