Add primaryTenantDomain support to PushNotificationData

[VihangaMunasinghe]

Purpose

Add primaryTenantDomain support to PushNotificationData to enable proper tenant resolution for organization-level push notification routing. This is required to correctly differentiate organization tenants from root tenants and build the correct relative API path for push notification delivery.

GitHub Issue

• Organization Handle is being returned as Organization ID in push notification data wso2/product-is#27438

Related PRs

1. identity-event-handler-notification: Fix tenant and sub-organization differentiation logic when building the PushNotificationData in push notification handler identity-event-handler-notification#384

Goals

• Introduce a primaryTenantDomain field in PushNotificationData and its Builder
• Include primaryTenantDomain in the additional data map when present, overriding the regular tenantDomain
• Build the correct relativePath based on organization and tenant context

Approach

• Added primaryTenantDomain as a new final field in PushNotificationData with corresponding Builder setter and getter
• Added a private buildRelativePath() method that constructs the relative path based on the combination of organizationId, primaryTenantDomain, and tenantDomain
• getAdditionalData() now includes the relativePath entry and conditionally overrides tenantDomain with primaryTenantDomain when set

User stories

As a system handling push notifications for organization users, I need the notification data to carry the primary tenant domain so that the push notification provider can route requests to the correct tenant API path.

Release note

Added primaryTenantDomain support to PushNotificationData for correct tenant resolution in organization-level push notification delivery.

Documentation

N/A - Internal model change with no direct user-facing documentation impact.

Training

N/A

Certification

N/A - Internal API change only.

Marketing

N/A

Automation tests

• Unit tests
  • N/A
• Integration tests
  • N/A

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes
• Ran FindSecurityBugs plugin and verified report? yes
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Samples

N/A

Migrations (if applicable)

N/A

Learning

N/A