fix(jobs): internal platform to nango-integration mapping

[mbani01]

This pull request updates the logic for determining the Nango integration name when checking the connection status in the nangoMonitoring.job.ts cron job. Instead of using a conditional inline check, it now delegates this responsibility to the platformToNangoIntegration helper function, which takes both int.platform and int.settings as arguments. This change should improve code readability and maintainability.

• Refactored the Nango integration name selection logic to use the platformToNangoIntegration helper function in nangoMonitoring.job.ts, replacing the previous inline conditional.

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