feat: support coalescing queue in kubernetes provider

[zirain]

This will help to reduce the cost when users applied mutiple resoureces in a short time window.

[netlify]

✅ Deploy Preview for cerulean-figolla-1f9435 ready!

Name	Link
🔨 Latest commit	66afefa
🔍 Latest deploy log	https://app.netlify.com/projects/cerulean-figolla-1f9435/deploys/6a8578d9ff4cbc00089baf26
😎 Deploy Preview	https://deploy-preview-9718--cerulean-figolla-1f9435.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[codecov]

Codecov Report

❌ Patch coverage is 90.00000% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.27%. Comparing base (e5ba4ba) to head (66afefa).

Files with missing lines	Patch %	Lines
internal/provider/kubernetes/controller.go	90.00%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9718   +/-   ##
=======================================
  Coverage   76.26%   76.27%           
=======================================
  Files         261      261           
  Lines       44351    44367   +16     
=======================================
+ Hits        33826    33840   +14     
- Misses       8284     8285    +1     
- Partials     2241     2242    +1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[guydc]

nice.

For the translation layer, do we have something similar in place? When a translation runs it blocks a publish, causing resource updates from gw-api to aggregate?

[zirain]

nice.

For the translation layer, do we have something similar in place? When a translation runs it blocks a publish, causing resource updates from gw-api to aggregate?

I debugging this for a while, this may cause status not updated if you use a long time windows(e.g. 1s), I'm still working on it. we setted up similar mechanism for XDSServer before.