[gateway] manage time drift on syncManager

[exalate-issue-sync]

If the Gateway is deployed on a server with temporal drift in the future compared to the Management API, the event sent to the Backend will never be read as the Gateway perform search queries using its own time reference (System.currentTimeInMillis).

This is a critical change so we have to be careful on it.

[exalate-issue-sync]

Sagar Chauhan commented: Environment = [https://am.management.v3-15-x.gravitee.dev/|https://am.management.v3-15-x.gravitee.dev/]
Version = 3.15.x
Result = Pass (/)

---

Regression testing has been completed for this ticket to ensure that when changes are made in the AM console, they work as expected within the gateway and the audit logs are displaying the correct information. The following areas have been tested:

• Domain creation
• Application creation
• User creation
• Identify provider creation (inline)
• MFA (Generic OTP)
• Bot detection creation
• Custom email template (Forgot password)