CBG-4538 tests: do not expect revSeqNo as a particular value

[torcolvin]

8497bc0 needs extension after merge release/anemone -> main.

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

Integration Tests

• GSI=true,xattrs=true https://jenkins.sgwdev.com/job/SyncGatewayIntegration/27/

[Copilot]

Pull Request Overview

This PR updates test assertions in import tests to handle non-deterministic revision sequence numbers. The changes address an issue where revision sequence numbers can start at the maximum CAS value of any previously deleted document, making specific value assertions unreliable.

• Replaced exact revision sequence number assertions with range checks
• Updated comments to explain why specific revSeqNo values cannot be asserted
• Changed from require.Equal to require.Greater for revision sequence comparisons