Handle depth -1 in isOrganization check

[Yoshani]

Purpose

When a suborg is deleted since stale data remains in SP_SHARED_APP table, when a shared parent app is updated those updates are tried to be done in non-existing deleted suborgs as well. For those nonexistent suborgs the hierarchy depth is returned as -1, and we can use this to return false in the isOrganization() check, which will in turn stop the other tasks related to shared app update from happening.

Related issues

• https://github.com/wso2-enterprise/asgardeo-product/issues/26168

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 45.86%. Comparing base (d137ed6) to head (fac884f).
Report is 5 commits behind head on main.

Files with missing lines	Patch %	Lines
...ement/service/util/OrganizationManagementUtil.java	0.00%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #154      +/-   ##
============================================
- Coverage     45.89%   45.86%   -0.04%     
  Complexity      442      442              
============================================
  Files            47       47              
  Lines          2983     2985       +2     
  Branches        358      359       +1     
============================================
  Hits           1369     1369              
- Misses         1458     1460       +2     
  Partials        156      156              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Yoshani]

Closing since return organizationDepth >= Utils.getSubOrgStartLevel(); line already handles this