feat: clarify max active bids per investor semantics

[blessme247]

📝 Description

This PR implements a maximum active bid per investor and also fixes syntax issues in the lib.rs file.

Closes #730

🎯 Type of Change

• Bug fix
• [ x] New feature
• Breaking change
• Documentation update
• Refactoring
• Performance improvement
• Security enhancement
• Other (please describe):

🔧 Changes Made

Files Modified

• src/lib.rs
• src/bid.rs
• src/test_bid.rs

New Files Added

Key Changes

🧪 Testing

• [x ] Unit tests pass
• Integration tests pass
• Manual testing completed
• No breaking changes introduced
• Cross-platform compatibility verified
• Edge cases tested

Test Coverage

tests active count for a new investor to be 0

📋 Contract-Specific Checks

• Soroban contract builds successfully
• WASM compilation works
• Gas usage optimized
• Security considerations reviewed
• Events properly emitted
• Contract functions tested
• Error handling implemented
• Access control verified

Contract Testing Details

📋 Review Checklist

• [ x] Code follows project style guidelines
• Documentation updated if needed
• [ x] No sensitive data exposed
• Error handling implemented
• [x ] Edge cases considered
• [ x] Code is self-documenting
• No hardcoded values
• Proper logging implemented

🔍 Code Quality

• Clippy warnings addressed
• Code formatting follows rustfmt standards
• No unused imports or variables
• Functions are properly documented
• Complex logic is commented

🚀 Performance & Security

• Gas optimization reviewed
• No potential security vulnerabilities
• Input validation implemented
• Access controls properly configured
• No sensitive information in logs

📚 Documentation

• README updated if needed
• [x ] Code comments added for complex logic
• API documentation updated
• Changelog updated (if applicable)

🔗 Related Issues

Closes #730
Fixes #
Related to #

📋 Additional Notes

🧪 How to Test

📸 Screenshots (if applicable)

⚠️ Breaking Changes

🔄 Migration Steps (if applicable)

---

📋 Reviewer Checklist

Code Review

• Code is readable and well-structured
• Logic is correct and efficient
• Error handling is appropriate
• Security considerations addressed
• Performance impact assessed

Contract Review

• Contract logic is sound
• Gas usage is reasonable
• Events are properly emitted
• Access controls are correct
• Edge cases are handled

Documentation Review

• Code is self-documenting
• Comments explain complex logic
• README updates are clear
• API changes are documented

Testing Review

• Tests cover new functionality
• Tests are meaningful and pass
• Edge cases are tested
• Integration tests work correctly

[drips-wave]

@blessme247 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[blessme247]

hi @Baskarayelu I've reviewed the failing CI workflow issue to be a non-existing issue. The CI check is currently flagging a closing delimiter issue in the contract implementation, which I've taken my time to review and can't find any open delimeter. Kindly review as well