fix: Added test for upstream target weight update and moved update method from PATCH to PUT in go-kong

[shivaygupta-dotcom]

Issue: #1894

Summary:

1. decK sync was failing when modifying upstream target weights in Konnect because the update operation in target CRUD used the PATCH endpoint, which is not supported by Konnect. This has been fixed by switching the update operation to use PUT instead.
2. Added test for both kong and konnect to verify nothing should break after moving to PUT endpoint.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 32.94%. Comparing base (d7a8236) to head (7155ebf).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1956   +/-   ##
=======================================
  Coverage   32.94%   32.94%           
=======================================
  Files          77       77           
  Lines        6975     6975           
=======================================
  Hits         2298     2298           
  Misses       4493     4493           
  Partials      184      184           

☔ View full report in Codecov by Sentry.
📢 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.

[Prashansa-K]

PR looks fine. We can merge post go-kong update.

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[shivaygupta-dotcom]

PR looks fine. We can merge post go-kong update.

@Prashansa-K Can you pls approve this, customer is asking release timeline for this.
https://konghq.atlassian.net/browse/FTI-7293?focusedCommentId=211067

[Prashansa-K]

PR looks fine. We can merge post go-kong update.

@Prashansa-K Can you pls approve this, customer is asking release timeline for this. https://konghq.atlassian.net/browse/FTI-7293?focusedCommentId=211067

Need a go-kong update. We can't release with a commit-id in go.mod
Plus, our CI is blocked.
Let them know that we can release by end of this week.

[shivaygupta-dotcom]

removed unused sum entries post running go mod tidy