fix(Secp256k1): resolve yParity type mismatch in verify

[Aboudjem]

Destructuring the OneOf union in verify() causes TypeScript to lose the correlation between address and the correct Signature type. After destructuring, signature becomes Signature<true> | Signature<false>, but recoverAddress expects Signature<true> (with required yParity).

This surfaces as a build error in downstream projects that type-check node_modules source files (e.g. next build), since ox ships raw .ts files.

The fix avoids destructuring branch-dependent properties upfront and instead accesses them from the options object after narrowing, so the type checker can resolve the correct union member.

Fixes wevm/viem#4379

[vercel]

@Aboudjem is attempting to deploy a commit to the Wevm Team on Vercel.

A member of the Team first needs to authorize it.

[Aboudjem]

The only CI failure is the Vercel deployment which needs team authorization — the code changes and Socket Security checks pass. Could a maintainer approve the Vercel bot when you get a chance? Happy to address any feedback on the code itself. Thanks!

[Aboudjem]

Hi — following up on this yParity fix. The only CI blocker is the Vercel deployment auth. Code changes and security checks all pass. Could a maintainer authorize the Vercel bot? Happy to address any code feedback. Thanks!

[Aboudjem]

Friendly ping — looks like the Vercel deployment check needs team authorization to run for external PRs. Could someone trigger it? The code changes and Socket Security checks are all passing.