optimize history repository performance with bulk insert

[yanosea]

Current Status

The current implementation of SaveAll in history repository performs individual
INSERT queries for each record, causing performance degradation when handling
large datasets.

Expected Changes

• Modify SaveAll method to use bulk insert
• Update ID assignment logic for bulk operations
• Ensure backward compatibility
• Add performance benchmarks before/after changes

Expected Benefits

• Reduced database load
• Improved throughput for batch operations
• Better scalability for large data sets

Acceptance Criteria

• Bulk insert implementation works correctly
• No regression in existing functionality
• Performance improvement is measurable
• Unit tests are updated/added