[JSDCLOUD-14932] Adding ORDER BY clause in SLA goals causes SLA to be missing in issues

When creating a SLA goal that has multiple priorities, adding a ORDER BY clause to the JQL will break the SLA on tickets

Example:

SLA to be visible in tickets

SLAs are not visible in tickets. Instead we see a warning icon and the following error message:

Could not load SLA.
SLA may be indexing due to configuration updates. If this persists check the SLA configuration.

Examining a HAR file when loading the issue will reveal the following error:

https://<site>.atlassian.net/rest/servicedesk/1/servicedesk/sla/issue/<issue-key>

{"message":"Unable to parse sla goal JQL","status-code":500,"stack-trace":""}

Remove the ORDER BY from the SLA goal, as this clause as no real utility in SLA goals.

No work has yet been logged on this issue.