Add opt-in browser bot-detection E2E coverage

[yfe404]

Goal

Add repeatable end-to-end checks for Cloakbrowser against these two external test pages:

• https://deviceandbrowserinfo.com/are_you_a_bot
• https://deviceandbrowserinfo.com/are_you_a_bot_interactions

Scope

• Extend test/e2e/fingerprint-spoofing.test.ts; do not add these checks to the unit suite.
• On the fingerprinting page, wait for raw results and assert that direct automation indicators such as hasWebdriverTrue, hasWebdriverInFrameTrue, isPlaywright, isHeadlessChrome, and isAutomatedWithCDP are false.
• On the interaction page, fill and submit the login form through the public humanizer tools, wait for raw results, and assert that suspiciousClientSideBehavior, superHumanSpeed, and hasCDPMouseLeak are false.
• Prefer accessible roles and labels over brittle CSS selectors.
• Keep failures diagnostic by including the parsed raw detection result in assertion messages.
• Add no runtime dependencies.

Verification

npm run build && npm run test:unit must remain green. The new E2E checks require Cloakbrowser plus internet access and are maintainer-run with npm run test:e2e; they are not expected to run in the factory sandbox.