Merge pull request Kong#233 from Kong/next

[kong] release 1.12.0

#### What this PR does / why we need it:
Releases Kong 1.12.0.

#### Special notes for your reviewer:
We had some issues with history when releasing 1.11.

For 1.12 and onward, the plan is is to use a merge commit for this PR (the release to main), and then merge main into next.

Merge pull request Kong#210 from Kong/next

[kong] release 1.11.0

Merge pull request Kong#204 from Kong/release/0.10.0

[kong] release 1.10.0 and reintegrate 1.9.0 commits

This PR releases the Kong chart version 1.10.0 and reintegrates `next` into `main`.

Reintegration of `next` into `main` is necessary because during the 1.9.0 release some commits were copied over to `main` from `next` by cherry-picking/rebasing, and therefore commits from `next` are not integrated into `main`. After this PR, all commits from `next` become ancestors of `main`.

The reintegration is a no-op from the perspective of file content - it only affects the relationships between commits in the commit tree.

From Kong#204

[kong] release 1.9.1

Release version 1.9.1. This version clarifies upgrade documentation for
1.9.0, and does not include functional changes of its own.

[kong] disable CRD installation for CI

[kong] Release Kong chart 1.8.0 to master

[kong] release 1.7.0

[kong] release 1.6.1

[kong] release 1.5.0

[kong] release chart version 1.4.1

Release chart version 1.4.1. This fixes an incorrect code example in the
1.4.0 UPGRADE.md section.