Issue Summary

When the subscribed Opsgenie is a subordinated version of the JSM subscription, all the data traffic from this Opsgenie should be allowed even when the IP allowlist feature has been enabled.

In the current design, the Opsgenie outbound IP list isn't whitelisted automatically when this feature is enabled on the JSM side and this list contains over 60 addresses required for adding, which might not be a great practice. This then stops the JSM integration data from Opsgenie to the JSM project.

Steps to Reproduce

1. Set up a JSM Premium project with a subordinate Opsgenie instance.
2. Configure the JSM integration on this Opsgenie instance.
   Documentation -> https://docs.opsgenie.com/docs/jiraservicedesk-integration
3. Enable the IP Allowlist feature on the JSM project without adding the Opsgenie outbound IP list.
4. Fire test alerts on the Opsgenie instance to verify if an issue will be created on the JSM project.

Expected Results

The Opsgenie Outbound IP List should be added automatically when the IP Allowlist feature is enabled and all integration data should be sent from Opsgenie to JSM flawlessly.

Actual Results

The Opsgenie OutBound IP List isn't on the allowlist, leading the JSM integration data is rejected with the following response body from the JSM side.

Workaround

Currently, we can only add all of the Outbound IP List and Atlassian Cloud IP Ranges which takes up over 60 entries on the allowlist, not very ideal and no room for setting up other IP entries on the list.