fix: adding a separate context for background requests (CM-798)

[ulemons]

Background Cache Refresh Implementation

Overview

This PR introduces background cache refresh functionality for the queryMembersAdvanced flow. The goal is to improve performance by updating cached results asynchronously while still serving stale data immediately to users.

Changes

1. Background Cache Refresh Functions

• Added refreshCacheInBackground() to refresh full query results.
• Added refreshCountCacheInBackground() to refresh count-only queries.
• Both functions execute asynchronously and do not block the main request/response cycle.

2. Database Connection Management

• Introduced separate database connections for background operations using getDbConnection(READ_DB_CONFIG()).
• Created new QueryExecutor instances for background tasks via pgpQx().
• Reused the existing connection pool — no manual cleanup required.

Result

These changes reduce latency for users while ensuring cached data stays fresh behind the scenes.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.