fix(fingerprint-generator): guard generated viewport dimensions

[tine1117]

Fixes #6.

The generated fingerprint network can still return screen records with zero viewport fields such as innerWidth, innerHeight, clientWidth, and clientHeight. Those values are easy to flag because they do not match a real browser viewport.

This change adds a small guard at fingerprint generation time:

• normalize zero viewport fields from the surrounding screen dimensions when the generated record is otherwise usable
• skip generated screens that still violate basic client <= inner <= outer viewport invariants
• cover the Chrome 100/macOS generation path and the zero-viewport normalization case with regression tests

This complements #544. That PR tightens future training records; this one protects the runtime generator from the current published network output as well.

Validation:

• corepack pnpm vitest run test/fingerprint-generator/generation.test.ts --reporter verbose
• corepack pnpm exec prettier packages/fingerprint-generator/src/fingerprint-generator.ts test/fingerprint-generator/generation.test.ts --check
• git diff --check
• Git Bash: npm exec --yes pnpm@10.33.4 -- build

Note: full pnpm lint is not clean on the current checkout because repo-wide Prettier reports existing formatting differences in untouched files. The two changed files pass Prettier directly.

@algora-pbc /claim #6

[barjin]

As mentioned under #544 , the right solution is to fix the fingerprint collection script.

Closing this PR now. Thank you for your contribution anyway!