Issue with API Deployment Synchronization After Force Restart of CP Node in APIM 4.3.0

[SameeraSI]

Description

API redeployments are not reflected in the Gateway after performing a forced restart (terminate and start) on the Control Plane node, due to cached queue IDs from previously deleted queues.

Steps to Reproduce

1. Set up a distributed deployment with a Gateway (GW) and Control Plane (CP) using APIM 4.3.0 (this issue might also be reproducible in an AIO setup).
2. Start both the GW and CP nodes.
3. Deploy an API and verify that it is successfully deployed to the GW.
4. Forcefully terminate (kill) the CP node process.
5. Restart the CP node.
6. Perform a change to the previously deployed API and redeploy it, or deploy a new API. The deployments will not be reflected in the GW nodes.

Version

wso2am-4.3.0

Environment Details (with versions)

No response