Decouple account_requests table from Eclipse database service and move to dedicated module

Problem

• The account_requests database table is currently implemented through the Eclipse database service in the eclipsefdn custom Drupal module.
• This creates a tight coupling between the account_requests implementation and the Eclipse database service.
• The account_requests table needs to be moved to a different database cluster, which requires a separate database connection and service.

Expected Behavior

• The account_requests table should use a dedicated database service that connects to the new cluster.
• The implementation should be decoupled from the existing Eclipse database service in the eclipsefdn module.

Proposed Solution

• Create a new Drupal module responsible for the account_requests database integration.
• Implement a new database service in this module that uses the database connection for the new cluster.
• Refactor existing code to use this new service instead of the Eclipse database service.