Fix: Safari compatibility for documentation navigation

[CHENJIAMIAN]

Summary

Fixed Safari browser navigation issues in three.js documentation across all sections (TSL, Global, and Core pages). Enhanced scroll handling specifically for Safari's iFrame navigation behavior while maintaining compatibility with other browsers.

Problem

Safari users experienced navigation failures where clicking documentation entries would show the wrong page portion or fail to scroll to the correct sections. This affected:

• TSL section entries (e.g., "Break", "PI")
• Global section entries
• NodeMaterial and other regular sections
• Specifically problematic in Safari on MacMini environments

Root Cause Analysis

The issue was not hash generation logic, but Safari's implementation of:

• scrollIntoView() within iFrames
• History API behavior in iFrame environments
• Rendering timing differences in Safari iFrames

Solution

• Safari Detection: Added accurate browser detection function
• Enhanced Scrolling: Implemented safariScrollToElement() with fallback methods
• Error Handling: Added try-catch blocks for scrollIntoView failures
• Extended Timing: 150ms delay for Safari iFrames vs 50ms for others
• Hash Fallback: Manual hash setting when Safari's normal method fails
• Backward Compatibility: Preserved existing behavior for Chrome/Firefox

Test Environment

• Primary: Safari on MacMini (reproduces reported issue)
• Secondary: Chrome/Firefox (ensure no regression)
• Target: All three.js documentation sections working correctly

Technical Implementation

// Safari-specific handling
function safariScrollToElement( elementId ) {
    // Try scrollIntoView with error handling
    // Fallback to manual position calculation
    // Extended rendering delay for iFrames
}

Fixes #32302
Addresses @Mugen87 feedback on Safari compatibility

[Mugen87]

This change does not fix the issue for me. Testing with Safari on a macMini. I have searched for break and clicked on the "Break" TSL entry but the iFrame shows the wrong portion of the page. Besides, searching for aonode and clicking on the "aoNode" entry of NodeMaterial also has the same issue. So this problem is not exclusive for the TSL/Global page but a general issue of Safari.

Since there is already another PR trying to fix the issue, please do not create new ones. If you want to contribute, share your thoughts in #32312.