changes to participants db

[pavliuc75]

Since we have expectedParticipantData now, we should consider save and access participant information (email, name, etc.,) here, and use Keycloak only for identity management, this will

• Save a lot of resources and time when processing recruitment/participants related operations.
• Save participant information in our database, instead of Keycloak database
• Have user information page back on Portal
• Requires changes to participants page, as information will not be stored in keycload anymore (or extra work)

Maybe also consider change Participants page --> Recruitment page, and remove deployed participants, since they should be managed in deployments

The process time is expected to reduce significantly for Participants and Deployments page on Portal, and we can keep rely on frontend to do pagination.