fix: mongo collecction with indexes max time

[franklinkim]

Description

Reimplement CollectionWithIndexesMaxTime with a context timeout (mongo-driver v2 dropped MaxTime) and fix mistakenly renamed CollectionWith* option functions.

Type of Change

• 🐛 Bug fix
• ✨ New feature
• 💥 Breaking change
• 📝 Documentation
• ♻️ Refactoring
• 🏃‍➡️ Performance
• ✅ Tests
• 🔐 Security
• 🔧 Build/CI

Changes

• CollectionWithIndexesMaxTime no longer no-op; wraps index creation in a context.WithTimeout using the given duration.
• Replaced IndexesContext field with IndexesMaxTime time.Duration on CollectionOptions.
• Renamed mistyped option funcs to match what they actually set: CollectionWithIndexesContext → CollectionWithCommitQuorumInt, CollectionWithIndexesQuorumMajority → CollectionWithCommitQuorumMajority, CollectionWithIndexesCommitQuorumString → CollectionWithCommitQuorumString, CollectionWithIndexesCommitQuorumVotingMembers → CollectionWithCommitQuorumVotingMembers.

Checklist

• My code adheres to the coding and style guidelines of the project.
• I have performed a self-review of my own code.
• I have commented on my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.