CBG-4798: add test for revID replicator write HLV generation

[gregns1]

CBG-4798

• Add test for replicator write via the revID pathway, asserting a HLV is generated on the write. Similar test was removed in CBG-4780: basic ISGR push and pull for 4.0 #7668 given the active replicator no longer uses < 4 protocol

Pre-review checklist

• Removed debug logging (fmt.Print, log.Print, ...)
• Logging sensitive data? Make sure it's tagged (e.g. base.UD(docID), base.MD(dbName))
• Updated relevant information in the API specifications (such as endpoint descriptions, schemas, ...) in docs/api

Dependencies (if applicable)

• Link upstream PRs
• Update Go module dependencies when merged

Integration Tests

• GSI=true,xattrs=true https://jenkins.sgwdev.com/job/SyncGateway-Integration/000/

[Copilot]

Pull Request Overview

This PR adds a test to verify that Hybrid Logical Vector (HLV) metadata is properly generated when documents are written through the rev ID replicator pathway. This test replaces similar functionality that was removed in PR #7668 when the active replicator stopped using protocol versions < 4.

• Add TestHLVUpdateOnRevReplicatorPut test function to verify HLV generation
• Test uses PutNewEditsFalse to simulate replicator write behavior
• Assertions verify HLV fields are correctly populated with source ID, version, and CAS values

[torcolvin]

Do you want to note in that we should have PutNewEditsFalse to make sure HLV is updated in #7658 or one of the tickets?

Do you think there's a difference between doing this with a REST api vs blip?

[bbrks]

Me and Greg synced up this morning on this which is how this ended up getting a new test written.

We intentionally do not want to have PutNewEditsFalse write a CV here. This is testing legacy rev handling. This is the same codepath as a 3.x BLIP replicator via PutExistingRevWithConflictResolution