Drop and turn off QPS and Burst setting

[nak3]

/area API
/kind cleanup

Please refer to #2755 (comment)

Upstream recommends that we should turn off it and use APF instead.

[pierDipi]

If we do this, I'd advise to coordinate with working groups if we plan to make breaking changes in this area, it seems we're suggesting to turn them off but that is only a partial solution.

I would actually suggest to allow turning them off but as opt-out config

[nak3]

I got an advice from internal team that disabling client-side rate-limiting is a GA goal of APF.

https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/1040-priority-and-fairness/README.md#graduation-criteria

APF allows us to disable client-side rate limiting without causing the apiservers to wedge/crash.

And there are still some efforts like kubernetes/kubernetes#109614

So yes, we should take care this carefully or actually we can just wait for GA of APF.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[dprotaso]

/lifecycle frozen

[dprotaso]

We should revisit this once our serving perf changes lands