Prepare release/3.1.4

[randmonkey]

What this PR does / why we need it:

Prepare for release 3.1.4, update CHANGELOG.

Which issue this PR fixes:

Part of #5911

Special notes for your reviewer:

PR Readiness Checklist:

Complete these before marking the PR as ready to review:

• the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (release/3.1.x@26abd3e). Click here to learn what that means.

Additional details and impacted files

@@               Coverage Diff               @@
##             release/3.1.x   #5920   +/-   ##
===============================================
  Coverage                 ?   72.0%           
===============================================
  Files                    ?     176           
  Lines                    ?   18306           
  Branches                 ?       0           
===============================================
  Hits                     ?   13183           
  Misses                   ?    4157           
  Partials                 ?     966           

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

[team-k8s-bot]

E2E (targeted) tests with KIND-based clusters were started at https:/Kong/kubernetes-ingress-controller/actions/runs/8829399670

[pmalek]

Shouldn't this target main branch instead of the release branch?

[randmonkey]

Shouldn't this target main branch instead of the release branch?

This does not include the entries that are not included in 3.1.x branch. Also, there are fixes that are specific to 3.1.x (bump golnag patch and x/net,protobuf packages).
Since the CHANGELOG is diverged in release/x.x.x and main, Can we fix changelogs in main after 3.1.4 released?

[pmalek]

Since the CHANGELOG is diverged in release/x.x.x and main, Can we fix changelogs in main after 3.1.4 released?

We can do it this way 👍 I thought we aimed at maintaining the CHANGELOG only in main 🤔