Config version limit

[tathagat2241]

Changes

• Version Limit Enforcement: Added #enforceVersionLimit() method to ConfigurationCollection that automatically cleans up old versions on every save() operation
• Asynchronous Execution: Cleanup runs via setImmediate() to avoid blocking the main save operation
• Batch Deletion: Deletes old versions in batches of 25 (DynamoDB batch write limit) for optimal performance
• Graceful Error Handling: Cleanup failures are logged but don't affect the main save operation
• Comprehensive Testing: Added 8 new test cases covering all cleanup scenarios, edge cases, and error handling

Technical Details

• Trigger: Cleanup runs automatically after each configuration create() (save)
• Target: Keeps newest 500 versions, deletes older versions beyond this limit
• Safety: Only affects Configuration entities (ElectroDB entity isolation via GSI)
• Performance: Uses DynamoDB batch operations and parallel deletion with Promise.all()

Please ensure your pull request adheres to the following guidelines:

• make sure to link the related issues in this description
• when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

Related Issues

https://jira.corp.adobe.com/browse/SITES-37650

Thanks for contributing!

[github-actions]

This PR will trigger a minor release when merged.