Update push authentication endpoint building instructions in build push auth app docs

[VihangaMunasinghe]

Purpose

This PR updates the "Build your own Push Notification Authenticator Application" tutorial to define the new variables and endpoints for push authentication. Specifically, it:

• Adds the relativePath attribute with its possible resolved paths to the push notification data attributes table.
• Documents the conditional building of the authentication API endpoint using either the relativePath (Option 1) or by building the full endpoint using a tenanted path, an organization path, or a tenant qualified organization aware path (Option 2).

Related Issue

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

Related PRs

• Fix tenant and sub-organization differentiation logic when building the PushNotificationData in push notification handler wso2-extensions/identity-event-handler-notification#384
• Add primaryTenantDomain support to PushNotificationData wso2-extensions/identity-notification-push#23

Test environment

• macOS
• Markdown structure checked via markdownlint-cli2

Security checks

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

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}