fix(auth): skip navigator lock when persistSession is false

[7ttp]

what

when persistSession: false is set, the auth client was still using navigator locks for cross-tab coordination. this caused NavigatorLockAcquireTimeoutError to appear in the console even though there's no shared state between tabs when sessions are stored in memory only.

why

navigator locks are used for cross-tab session coordination. when persistSession: false:

• sessions are stored in memory only (not localStorage)
• each tab has its own isolated session
• no cross-tab coordination is needed
• the lock acquisition can fail and throw errors unnecessarily

this is consistent with how BroadcastChannel is already handled in the same file, which also checks persistSession before enabling cross-tab communication.

how

added his.persistSession check to the condition for using avigatorLock. when persistSession: false the client now uses lockNoOp instead.

closes #1517

[coveralls]

coverage: 95.367% (+14.2%) from 81.176%
when pulling 65946b9 on 7ttp:bug2
into 0baaf06 on supabase:master.