fix: forget should be changed to addratelimited

[raylan-chen]

Type of change:

• Bugfix
• New feature provided
• Improve performance
• Backport patches
• Documentation
• Refactor
• Chore
• CI/CD or Tests

What this PR does / why we need it:

I am new to programming and not familiar with golang and apisix-ingress-controller, so I am just trying to fix the bugs in the code as per the changes mentioned in the #2348.

The previous line of log code mentions the need for retry, but the next line of code c.workqueue.forget(obj) performs a forget operation, which as mentioned in the issue should be changed to addratelimited.

Regarding the test case, since I'm not familiar with golang and apisix-ingress-controller, I can only offer a bit of a beginner's idea:
When the function parameter errorigin is null,

• c.workqueue.forget will be called;
• "pluginconfig" "success" in MetricsCollector corresponding tag count + 1.

When errorigin is not found in k8serror and types.event is not equal to eventdelete ,

• log mentions ignore ;
• c.workqueue.forget will be called.

When other cases are encountered,

• record the log and the log should mention that retry ;
• c.workqueue.addratelimited should be called;
• "pluginconfig" "failure" in MetricsCollector corresponding tag count + 1.

Is there a better bug fix? Maybe we can try:
1. record the number of times adding an item to the workqueue, when the number of times reaches a certain threshold, give up the retry, and trigger the alarm mechanism;
2. introduce a fallback mechanism, gradually increase the retry interval, to avoid frequent failures bring too much load.

Closely linked to issue https://github.com//issues/2348.

Pre-submission checklist:

• Did you explain what problem does this PR solve? Or what new features have been added?
• Have you added corresponding test cases?
• Have you modified the corresponding document?
• Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first