refactor(orb): use clear, consistent and well described naming for splitmix32's readability

[alamenai]

What

The current implementation of splitmix32 is difficult to understand, as it relies on shortcuts and rarely used symbols.

This reduces readability and makes it harder to grasp how the function fits into the overall logic and the structure of the Orb component.

Additionally, it relies on hard-coded values rather than clearly defined variables or constants, which further impacts clarity and maintainability.

I added a link for more explanation of the function ( From GitHub ) - Feel free to suggest another link -

[vercel]

@alamenai is attempting to deploy a commit to the ElevenLabs Team on Vercel.

A member of the Team first needs to authorize it.