Test repeated finite CouchDB connection ownership

[vrtmrz]

This follow-up protects finite CouchDB connection ownership by formatting the merged implementation and covering repeated one-shot Security Seed refreshes.

Summary

• Apply the repository's formatting to LiveSyncReplicator without changing its behaviour.
• Exercise two repeated one-shot cycles, each of which creates a Security Seed connection and a replication connection.
• Verify that every temporary remote database handle is closed exactly once.

Rationale

PR #112 fixed the production ownership issue. This follow-up keeps that implementation unchanged while protecting the repeated refresh boundary against regression.

Verification

• vitest run src/replication/couchdb/LiveSyncReplicator.unit.spec.ts — 33 tests passed.
• npm run check:types
• Prettier check for the changed files