fix: health score retention

[gaspergrom]

Note

Medium Risk
Changes the core query logic used to compute retention health score by excluding activities not in activityTypes_filtered, which can shift reported retention rates. Risk is moderate because it affects analytics outputs but does not touch security or data writes.

Overview
Updates health_score_retention.pipe to filter both current- and previous-quarter member cohorts by allowed (type, platform) pairs from activityTypes_filtered (in both the project-scoped and union datasource branches).

This makes the retention health score consistent with other activity-based metrics by excluding disallowed activity types/platforms from the retained-member calculations.

^{Written by Cursor Bugbot for commit da10c25. This will update automatically on new commits. Configure here.}

[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.

[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.