Rate limiting doesn't get properly configured in DP when switching from API Level to Resource Level

[O-sura]

Description:
In the APK CP to DP flow, after creating an API if the user enables the API level rate limiting first and then switch to resource level rate limiting, still the API level rate limiting which applied earlier gets applied instead of the resource level configuration. The observation was after switching to resource level and updating the API with new resource level ratelimit configs the API level RateLimitPolicies CR need to be removed but instead it stays as it is so even with the new settings the API level RatelimitPolicy CR gets the high priority hence the new settings doesn't get properly configured in the DP side

Steps to reproduce:

1. Create an API using APIM
2. Enable API level rate limiting(API Configurations > Resources) for that created API and deploy.
3. Invoke and Test whether the rate limiting works and it should work as intended.
4. Next, switch the rate limiting from API level to resource level using the radio button. Then add the rate limiting to some of the resources and try to invoke them.