Fix Tenant ID Addition of Newly Added Scopes of Exiting System APIs

[dhaura]

Purpose

• $Subject

Related Issues

• Newly Added Internal Org Scopes for an Existing API are Not Allowed for Child Organization Admin product-is#21306

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 40.11%. Comparing base (a52bcdc) to head (6948c4b).
Report is 59 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #6018      +/-   ##
============================================
- Coverage     40.17%   40.11%   -0.06%     
- Complexity    14170    14202      +32     
============================================
  Files          1734     1736       +2     
  Lines        116957   117376     +419     
  Branches      20022    20185     +163     
============================================
+ Hits          46988    47090     +102     
- Misses        62750    63052     +302     
- Partials       7219     7234      +15     

Flag	Coverage Δ
unit	23.96% <100.00%> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[jenkins-is-staging]

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/11294207631

[jenkins-is-staging]

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/11294207631
Status: success

[jenkins-is-staging]

Approving the pull request based on the successful pr build https://github.com/wso2/product-is/actions/runs/11294207631

[dhaura]

• Closing this PR since the purpose of this PR is achieved through a different implementation - Fix Tenant ID Addition of Newly Added Scopes of Exiting System APIs #6024.

[dhaura]

• When an API belongs to all tenants, in db the tenant id is set to null for all API scopes. Therefore, having tenant id equals to zero can cause confusion in the service layer. Therefore, it was finally decided to bring the check to the DAO layer.
• Hence, the PR was reopened.

[jenkins-is-staging]

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/11366348597

[jenkins-is-staging]

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/11366348597
Status: success

[jenkins-is-staging]

Approving the pull request based on the successful pr build https://github.com/wso2/product-is/actions/runs/11366348597