Konnect entities: KonnectAuthConfiguration reconciler

[pmalek]

Problem statement

Implement KonnectAuthConfiguration reconciler.

For details see https://docs.google.com/document/d/1TxW2ovqPRm-w1td1e_V0CyaET4lpiEBCJ7hiYMZJqng/edit#heading=h.xeiruffwggdz

Proposed solution

• Implementation of this reconciler can be based off of the PoC branch (https://github.com/Kong/gateway-operator/commits/konnect-entities/).

• Kong Configuration CRDs (like Consumer, Kong's Service etc) will have to contain references to KonnectAuthConfiguration hence its definition has to live outside of KGO to prevent import cycles (between KIC and KGO, as well as https://github.com/Kong/kubernetes-configuration and KGO). For this reason this CRD and its types has to live in https://github.com/Kong/kubernetes-configuration

• Introduction of this reconciler should be accompanied by introduction of a toggle for konnect related reconcilers which will allow disabling/enabling them when needed.

Acceptance criteria

• KGO can be configured with a CRD which will contain (and later on be able to reference) Konnect API token for communication with Konnect
  • Done in feat(konnect): add KonnectAPIAuthConfiguration reconciler #456
• Status fields of this CRD are filled with information such as
  • Indication whether the token is valid (using /v3/organizations/me endpoint which works for both user and service PATs in Konnect.
• As a User I can use secretRef to reference secret holding my Konnect token as an alternative to explicit token inside the KonnectAPIAuthConfiguration
  • feat(konnect): support Secrets in KonnectAPIAuthConfiguration #459 implements that.

[czeslavo]

Looks like it's done 👍