Use Konnect SDK for managing control plane in Konnect integration

[randmonkey]

Is there an existing issue for this?

• I have searched the existing issues

Does this enhancement require public documentation?

• I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

Problem Statement

Similar to #3550, we could use Konnect SDK instead of manually creating clients and composing requests for managing control planes and roles.
For other functions (Node uploading and license fetching), they are using KIC specific path. We are not sure if we can use the SDK for the functions.

Proposed Solution

• Use interfaces in https://github.com/Kong/sdk-konnect-go instead of own clients for requests to Konnect about control plane and roles.

Additional information

No response

Acceptance Criteria

• Types in https://github.com/Kong/sdk-konnect-go instead of own client to operate Konnect APIs are used if available

[pmalek]

#6620 and #6648 have been merged.

Other clients that are located in

• https://github.com/Kong/kubernetes-ingress-controller/blob/013fe565072ee62452e5321fc2c5a3680b80c721/internal/konnect/license
• and https://github.com/Kong/kubernetes-ingress-controller/blob/013fe565072ee62452e5321fc2c5a3680b80c721/internal/konnect/nodes

use KIC specific APIs:

• <BASE_URL>/kic/api/control-planes/<CP_ID>/v1/licenses
• <BASE_URL>/kic/api/control-planes/<CP_ID>/v1/kic-nodes

which are not available in https://github.com/Kong/sdk-konnect-go/.