fix: handle null pagination parameters in latest event search query

Ensure proper defaults are used when pagination parameters are not
provided, this helps to have a query working for all DBs especially
SQL Server to avoid

```
The ORDER BY clause is invalid in views, inline functions, derived
tables, subqueries, and common table expressions, unless TOP, OFFSET or
FOR XML is also specified.
```

(cherry picked from commit 7fc4535)

Author: jgiovaresco

gravitee-apim-repository/gravitee-apim-repository-jdbc/src/main/java/io/gravitee/repository/jdbc/management/JdbcEventLatestRepository.java

@@ -75,6 +75,9 @@ public class JdbcEventLatestRepository extends JdbcAbstractRepository<Event> imp
     public List<Event> search(EventCriteria criteria, Event.EventProperties group, Long page, Long size) {
         log.debug("JdbcEventLatestRepository.search({})", criteriaToString(criteria));
 
+        var pageNumber = page != null ? page : 0;
+        var pageSize = size != null ? size : 10;
+
         final List<Object> args = new ArrayList<>();
         var select = """
             WITH PagedEvents AS (%s)
@@ -86,7 +89,7 @@ WITH PagedEvents AS (%s)
                 LEFT JOIN %s evo ON evt.id = evo.event_id
             ORDER BY evt.updated_at ASC, evt.id ASC
             """.formatted(
-                buildSelectIn(criteria, group, page, size, args),
+                buildSelectIn(criteria, group, pageNumber, pageSize, args),
                 tableName,
                 EVENT_PROPERTIES,
                 EVENT_ENVIRONMENTS,