CBG-5017 Resync: make sure to create HLV if non exists

[torcolvin]

NOTE: This may be superseded by #7892 , but this would be a very low risk way to fix resync in 4.0.2

Resync: make sure to create HLV if non exists

This fixes the error message:

Error updating doc %s: _vv: nil xattr value not allowed 

and allows a legacy rev to be resynced.

NOTE: do not merge yet, might fix as part of CBG-3690.

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/SyncGatewayIntegration/0000/

[Copilot]

Pull Request Overview

This PR fixes a bug where resyncing a legacy document (one without an HLV) would fail with a "nil xattr value not allowed" error. The fix ensures that an HLV is created during the resync operation if one doesn't already exist.

Key Changes:

• Added call to updateHLV in the resync operation to create HLV when missing
• Enhanced test coverage to verify resync works for both legacy docs (without HLV) and modern docs (with HLV)

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
db/database.go	Added HLV creation during document resync operation
db/database_test.go	Extended test to cover both pre-4.0 (no HLV) and post-4.0 (has HLV) scenarios