feat(providers): provide the ability to send to include_external_user…

[L-U-C-K-Y]

What changed? Why was the change needed?

Implements: https://github.com/novuhq/novu/issues/3479#issue-1721795062, https://discord.com/channels/895029566685462578/1185702635219714219/1185702635219714219

This pull request enhances the functionality of the OneSignal push notification provider by adding support for targeting users via external user IDs. It includes changes to the provider's main class and its test suite to accommodate this new feature.

• Provider Class Changes:

  • Added oneSignalOptions to the overrides in the OneSignalPushProvider class to support targeting via include_external_user_ids or include_player_ids based on the useExternalUserIds flag.

• Interface Changes:

  • Updated the IPushOptions interface to include the new oneSignalOptions field with an optional useExternalUserIds boolean property.

• Test Suite Additions:

  • Added new tests to verify that include_external_user_ids is used when useExternalUserIds is true.
  • Added tests to ensure include_player_ids is used when useExternalUserIds is false.
  • Added tests to confirm that include_player_ids is the default when oneSignalOptions is not provided.…_ids instead of include_player_ids

Screenshots

Expand for optional sections

### Related enterprise PR ### Special notes for your reviewer

[netlify[bot]]

👷 Deploy request for novu-stg-vite-dashboard-poc pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	3af6f05a8fd3ff2f78809fe9a944d1dae21ceedf

[suplere]

Hello, this solution still use old API. The old API may be deprecated or even disabled over time. You use include_external_user_ids - but with old API.

[L-U-C-K-Y]

Hello, this solution still use old API. The old API may be deprecated or even disabled over time. You use include_external_user_ids - but with old API.

I agree, we should use this one, it's the more proper way: https://github.com/novuhq/novu/pull/6976