Switch to new pagination header mechanism with better fallback

When storing SQL based pagination headers, the DAO + original query will be stored to allow for repeating the query on subsequent requests. Additional logic has been added for best effort fallbacks as well.

core/src/main/java/org/eclipsefoundation/core/model/CacheRecorder.java

@@ -20,6 +20,7 @@ import javax.ws.rs.container.ContainerResponseContext;
 import javax.ws.rs.core.MultivaluedMap;
 
 import org.eclipse.microprofile.config.inject.ConfigProperty;
+import org.eclipse.microprofile.context.ManagedExecutor;
 import org.eclipsefoundation.core.helper.ParameterHelper;
 import org.slf4j.Logger;
 import org.slf4j.LoggerFactory;
@@ -55,6 +56,8 @@ public abstract class CacheRecorder<T> {
     @Inject
     protected ParameterHelper paramHelper;
 
+    @Inject
+    ManagedExecutor exec;
     /**
      * Generates the record and does internal tracking of the key for the request. The tracked key is only updated on new
      * cache entries, and fetching will not modify this time or extend it.