Run Legal CRON (/updateLegalTagStatus) API in partition context only

Multiple users have reported they couldn't use ~100 legal tags for Data Ingestion workflow. It seems Legal tags were set to invalid incorrectly. While triaging the issue, we found Legal CRON API (/updateLegalTagStatus) malfunctioned. If we have more than data-partitions, then Legal CRON API will pull COO file for first data-partition and run the business rule for all data-partitions in context of that file.

We checked and saw an issue was reported on this: Compliance API loops through all tenants but fetches tenant countries for the tenant in the RequestInfo. It is marked as closed but the issue remains; Related issue: #70 (closed)

In addition, we see frequent timeout response from this endpoint described by issue: updateLegalTagStatus API throwing 509 errors Related issue: #106

The fix for this issue updates the API contract and requires invocation of the API for each data-partition as oppose to current implementation where one API call that run business rule on all data-partitions.

We have checked the CRON trigger (client) for API and found we have inconsistent implementation.

Azure (trigger) and GC (trigger) are calling the Legal CRON API (/updateLegalTagStatus) for each data-partition in an environment, where as AWS calls the API only once. We are unsure about IBM.

Once this change is merged, no change is expected on CRON trigger for Azure and GC but requires update for AWS and possibly for IBM.