Fix race condition in analytics increment

[gul-ahmad]

Problem

The current implementation of the analytics increment method is susceptible to race conditions. In high-concurrency situations, this could lead to duplicate rows being created instead of proper increments.

Solution

Added database row-level locking using lockForUpdate() within a transaction to ensure atomic operations:

• Used lockForUpdate() to prevent concurrent access to the same analytics row
• Wrapped operations in a transaction for atomicity
• Added proper locking when checking max analytics limit

Changes

• Modified increment() method in DatabaseAnalyticsRepository to use transactions and row-level locking
• Ensures only one row is created even with concurrent requests
• Maintains existing functionality while fixing the race condition