Avoid pulling all the API metadata from /internal/data/v1/apis endpoint

[VirajSalaka]

Describe your problem(s)

Currently, the choreo connect calls /internal/data/v1/apis endpoint during startup and pull all the APIs. This is used to validate subscriptions, to identify default apis and to identify blocked APIs.

But for subscription validation, the choreo connect can retrieve the API UUID using the runtime artifact fetched from API manager. For default APIs and blocked APIs, a separate query parameter conditions are introduced and we can rely on that. Apart from that, it is not necessary to call the /apis endpoint for each API deploy event received.

Describe your solution

How will you implement it

---

Optional Fields

Related Issues:

Suggested Labels:

Suggested Assignees:

[VirajSalaka]

Moving forward, we need this information to be included within the deployment.json file. This could reduce the load on the API Manager significantly. There are edge cases where #2985 cannot handle. (ex: If there is a blocked api which remains undeployed by the time choreo connect starts, that API would remain unblocked when the deployment is triggered)