fix: store full precision for total hours played

Remove rounding to 2 decimals in UpdatePlaytimeUseCase when updating TotalHoursPlayed.
Reasons:
- Avoid loss of precision for accumulated playtime.
- Ensure backend stores the most accurate value, allowing the client to display or round as needed.
- Prevent potential floating-point errors from repeated small increments.
- Keep total hours played more consistent and reliable for reporting or analytics.

Author: DevD4v3

src/UseCases/Testers/UpdatePlaytime.cs

@@ -28,12 +28,11 @@ public async Task<Result> ExecuteAsync(string accessKey, UpdatePlaytimeRequest r
         if (validationResult.IsFailed())
             return validationResult.Invalid();
 
-        double roundedHours = Math.Round(request.HoursPlayed, 2);
         int affectedRows = await dbContext
             .Set<Tester>()
             .Where(t => t.AccessKey == accessKey)
             .ExecuteUpdateAsync(setters => setters
-                .SetProperty(t => t.TotalHoursPlayed, t => t.TotalHoursPlayed + roundedHours));
+                .SetProperty(t => t.TotalHoursPlayed, t => t.TotalHoursPlayed + request.HoursPlayed));
 
         return affectedRows == 0 ? Result.NotFound() : Result.Success();
     }