[Feat]: Use Jpa to paginate in JpaDatabasePushNotificationConfigStore

[ehsavoie]

Is your feature request related to a problem? Please describe.

In the JpaDatabasePushNotificationConfigStore implementation, the pagination is currently handled in-memory after fetching all records. This could lead to performance issues with large datasets. We should move the pagination logic to the database query level for better scalability and to ensure deterministic ordering.

Describe the solution you'd like

We should move the pagination logic to the database query level for better scalability and to ensure deterministic ordering.

Describe alternatives you've considered

No response

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[Sathyvs]

Hi @ehsavoie , Is this already in progress? Or Can i work on it ?

[ehsavoie]

@Sathyvs you can work on it. I was thinking using something similar to what is used with the taskStore.

[Sathyvs]

@ehsavoie Thank you for the reference, I will check it out and send a PR for review

[Sathyvs]

@ehsavoie is it ok to introduce new timestamp fields in the JpaPushNotificationConfig for sorting for the purpose of pagination ? I believe the config_id is a type 4 uuid and cannot be used to sort on its own, is that correct ?